From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Stabellini Subject: Re: Xen's Linux kernel config options V2 Date: Wed, 4 Feb 2015 14:57:03 +0000 Message-ID: References: <54905BF1.2050608@suse.com> <54D1FA55.9000503@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <54D1FA55.9000503@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: David Vrabel Cc: Juergen Gross , "xen-devel@lists.xensource.com" , "Ian.Campbell@citrix.com" , Jan Beulich , Boris Ostrovsky List-Id: xen-devel@lists.xenproject.org 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 >