From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [RFC v1] x86, platform, xen, kconfig: add xen defconfig helpers Date: Thu, 5 Jun 2014 10:44:13 +0100 Message-ID: <53903BED.3070407@citrix.com> References: <1401929299-16550-1-git-send-email-mcgrof@do-not-panic.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WsUDZ-0001mH-E3 for xen-devel@lists.xenproject.org; Thu, 05 Jun 2014 09:44:17 +0000 In-Reply-To: <1401929299-16550-1-git-send-email-mcgrof@do-not-panic.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: "Luis R. Rodriguez" , xen-devel@lists.xenproject.org Cc: "Luis R. Rodriguez" List-Id: xen-devel@lists.xenproject.org On 05/06/14 01:48, Luis R. Rodriguez wrote: > From: "Luis R. Rodriguez" > > Signed-off-by: Luis R. Rodriguez > --- > > Hey folks, shiny kvm has a shortcut 'make kvmconfig' on the > kernel, and I thought this was a good idea so wanted to add a > respective helper for xen. Contrary to kvm though we can have > a dom0 and a guest kernel configuration. As it is right now this > patch bundles the same exact options for both, but figured > folks might already have special configs for both different > types. What options would we want as default *upstream* for each > of these ? This looks like a good idea but I would only have one Xen option. There are so few options that only apply to dom0 that it doesn't make sense to have a dom0 option. > --- /dev/null > +++ b/arch/x86/configs/xen_dom0.config Make this xen.config > @@ -0,0 +1,37 @@ > +CONFIG_XEN=y > +CONFIG_XEN_DOM0=y > +CONFIG_XEN_PVHVM=y > +CONFIG_XEN_MAX_DOMAIN_MEMORY=500 > +CONFIG_XEN_SAVE_RESTORE=y > +# CONFIG_XEN_DEBUG_FS is not set > +CONFIG_XEN_PVH=y > +CONFIG_PCI_XEN=y > +CONFIG_XEN_PCIDEV_FRONTEND=m > +CONFIG_XEN_BLKDEV_FRONTEND=m > +CONFIG_XEN_BLKDEV_BACKEND=m > +CONFIG_NETXEN_NIC=m Remove this as it isn't a Xen related option, but an ethernet driver. > +CONFIG_XEN_NETDEV_FRONTEND=m > +CONFIG_XEN_NETDEV_BACKEND=m > +CONFIG_INPUT_XEN_KBDDEV_FRONTEND=y > +CONFIG_HVC_XEN=y > +CONFIG_HVC_XEN_FRONTEND=y > +# CONFIG_TCG_XEN is not set Enable as a module. > +CONFIG_XEN_WDT=m > +CONFIG_XEN_FBDEV_FRONTEND=y > +CONFIG_XEN_BALLOON=y > +CONFIG_XEN_BALLOON_MEMORY_HOTPLUG=y > +CONFIG_XEN_SCRUB_PAGES=y > +CONFIG_XEN_DEV_EVTCHN=m > +CONFIG_XEN_BACKEND=y > +CONFIG_XENFS=m > +CONFIG_XEN_COMPAT_XENFS=y > +CONFIG_XEN_SYS_HYPERVISOR=y > +CONFIG_XEN_XENBUS_FRONTEND=y > +CONFIG_XEN_GNTDEV=m > +CONFIG_XEN_GRANT_DEV_ALLOC=m > +CONFIG_SWIOTLB_XEN=y > +CONFIG_XEN_PCIDEV_BACKEND=m > +CONFIG_XEN_PRIVCMD=m > +CONFIG_XEN_ACPI_PROCESSOR=m > +# CONFIG_XEN_MCE_LOG is not set > +CONFIG_XEN_HAVE_PVMMU=y David