From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: Juergen Gross <jgross@suse.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Ian.Campbell@citrix.com" <Ian.Campbell@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: Xen's Linux kernel config options V2
Date: Wed, 4 Feb 2015 14:57:03 +0000 [thread overview]
Message-ID: <alpine.DEB.2.02.1502041446040.29696@kaball.uk.xensource.com> (raw)
In-Reply-To: <54D1FA55.9000503@citrix.com>
On Wed, 4 Feb 2015, David Vrabel wrote:
> On 16/12/14 16:21, Juergen Gross wrote:
> > Hi,
> >
> > This is a design proposal for a rework of the config options on the
> > Linux kernel which are related to Xen.
> >
> > The need to do so arose from the fact that it is currently not
> > possible to build the Xen frontend drivers for a non-pvops kernel,
> > e.g. to run them in a HVM-domain. There are more drawbacks in the
> > current config options to which I'll come later.
> >
> > Option Selects Depends
> > ----------------------------------------------------------------------
> > XEN
> > XEN_PV(x86) XEN_HAVE_PVMMU
> > PARAVIRT
> > PARAVIRT_CLOCK
> > XEN_PVH(x86) XEN_PVHVM
> > PARAVIRT
> > PARAVIRT_CLOCK
> > XEN_PVHVM PARAVIRT
> > PARAVIRT_CLOCK
PARAVIRT_CLOCK and PARAVIRT are x86 specific.
Given that there is no CONFIG_PV or CONFIG_PVH or even CONFIG_PVHVM on
arm and arm64 as there is just one type of guest, I would rather just
have CONFIG_XEN there.
> > XEN_BACKEND SWIOTLB_XEN(arm,arm64) XEN_PV(x86) ||
> > XEN_PVH(x86) ||
> > XEN_PVHVM
> > XEN_BLKDEV_BACKEND
> > XEN_PCIDEV_BACKEND(x86)
> > XEN_SCSI_BACKEND
> > XEN_NETDEV_BACKEND
> > PCI_XEN(x86) SWIOTLB_XEN
> > XEN_DOM0 XEN_BACKEND XEN_PV(x86) ||
> > PCI_XEN(x86) XEN_PVH(x86)
> > XEN_ACPI_HOTPLUG_MEMORY XEN_STUB
> > XEN_ACPI_HOTPLUG_CPU XEN_STUB
> > XEN_MCE_LOG(x86)
> > XEN_MAX_DOMAIN_MEMORY(x86)
> > XEN_SAVE_RESTORE(x86)
> > XEN_DEBUG_FS
> > XEN_WDT
> > XEN_BALLOON
> > XEN_SELFBALLOONING XEN_TMEM
> > XEN_BALLOON_MEMORY_HOTPLUG
> > XEN_SCRUB_PAGES
> > XENFS XEN_PRIVCMD
> > XEN_COMPAT_XENFS
> > XEN_SYS_HYPERVISOR
> > XEN_DEV_EVTCHN
> > XEN_GNTDEV
> > XEN_GRANT_DEV_ALLOC
> > SWIOTLB_XEN
> > XEN_TMEM
not available on arm and arm64
> > XEN_PRIVCMD
> > XEN_STUB(x86_64) BROKEN
> > XEN_ACPI_PROCESSOR(x86)
> > XEN_HAVE_PVMMU
x86 specific
> > XEN_EFI(x64)
FYI soon to be available on arm
> > XEN_XENBUS_FRONTEND
> > XEN_FRONTEND XEN
> > XEN_XENBUS_FRONTEND
> > XEN_FBDEV_FRONTEND INPUT_XEN_KBDDEV_FRONTEND
> > XEN_BLKDEV_FRONTEND
> > HVC_XEN_FRONTEND HVC_XEN
> > TCG_XEN
> > XEN_PCIDEV_FRONTEND PCI_XEN
x86 specific for the moment
> > XEN_SCSI_FRONTEND
> > INPUT_XEN_KBDDEV_FRONTEND
> > XEN_NETDEV_FRONTEND
> > XEN_PLATFORM_PCI
definitely x86 only
> This looks fine to me.
>
> David
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
next prev parent reply other threads:[~2015-02-04 14:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 16:21 Xen's Linux kernel config options V2 Juergen Gross
2015-01-09 19:02 ` Konrad Rzeszutek Wilk
2015-02-04 0:48 ` Luis R. Rodriguez
2015-02-04 4:58 ` Juergen Gross
2015-02-05 23:59 ` Luis R. Rodriguez
2015-02-06 0:11 ` Luis R. Rodriguez
2015-02-04 8:29 ` Jan Beulich
2015-02-06 1:19 ` Luis R. Rodriguez
2015-01-19 13:28 ` Ian Campbell
2015-01-19 13:59 ` Jan Beulich
2015-02-04 0:50 ` Luis R. Rodriguez
2015-02-06 23:25 ` Luis R. Rodriguez
2015-02-06 23:26 ` Luis R. Rodriguez
2015-02-04 10:54 ` David Vrabel
2015-02-04 14:57 ` Stefano Stabellini [this message]
2015-02-04 15:02 ` Ian Campbell
2015-02-04 15:06 ` Stefano Stabellini
2015-02-06 1:28 ` Luis R. Rodriguez
2015-02-06 12:07 ` Stefano Stabellini
2015-02-06 22:51 ` Luis R. Rodriguez
2015-02-08 11:28 ` Stefano Stabellini
2015-02-12 4:29 ` Luis R. Rodriguez
2015-02-06 22:54 ` Luis R. Rodriguez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1502041446040.29696@kaball.uk.xensource.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=jgross@suse.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.