[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150113190346.GB27566@wotan.suse.de>
Date: Tue, 13 Jan 2015 20:03:47 +0100
From: "Luis R. Rodriguez" <mcgrof@...e.com>
To: Julien Grall <julien.grall@...aro.org>
Cc: "Luis R. Rodriguez" <mcgrof@...not-panic.com>, hpa@...or.com,
josh@...htriplett.org, sam@...nborg.org,
Michal Marek <mmarek@...e.cz>,
Randy Dunlap <rdunlap@...radead.org>,
Ian Campbell <Ian.Campbell@...rix.com>, kvm@...r.kernel.org,
x86@...nel.org, linux-kernel@...r.kernel.org, mtosatti@...hat.com,
Pekka Enberg <penberg@...nel.org>, fengguang.wu@...el.com,
levinsasha928@...il.com, David Rientjes <rientjes@...gle.com>,
xen-devel@...ts.xenproject.org, Borislav Petkov <bp@...e.de>,
David Vrabel <david.vrabel@...rix.com>, bpoirier@...e.de
Subject: Re: [Xen-devel] [PATCH v2 2/2] x86, arm, platform, xen, kconfig:
add xen defconfig helper
On Mon, Dec 15, 2014 at 11:58:34AM +0000, Julien Grall wrote:
> Hello Luis,
>
> On 09/12/14 23:35, Luis R. Rodriguez wrote:
> > From: "Luis R. Rodriguez" <mcgrof@...e.com>
> >
> > This lets you build a kernel which can support xen dom0
> > or xen guests by just using:
> >
> > make xenconfig
> >
> > on both x86 and arm64 kernels. This also splits out the
> > options which are available currently to be built with x86
> > and 'make ARCH=arm64' under a shared config.
>
> I guess this is also working for arm (32bits)?
Yeap!
>
> > diff --git a/kernel/configs/xen.config b/kernel/configs/xen.config
> > new file mode 100644
> > index 0000000..d2ec010
> > --- /dev/null
> > +++ b/kernel/configs/xen.config
> > @@ -0,0 +1,30 @@
> > +# generic config
> > +CONFIG_XEN=y
> > +CONFIG_XEN_DOM0=y
> > +CONFIG_PCI_XEN=y
> > +CONFIG_XEN_PCIDEV_FRONTEND=m
> > +CONFIG_XEN_BLKDEV_FRONTEND=m
> > +CONFIG_XEN_BLKDEV_BACKEND=m
> > +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=m
> > +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
>
> The common fragment config looks good for both ARM32 and ARM64:
>
> Acked-by: Julien Grall <julien.grall@...aro.org>
Can someone apply this? Who should this go through?
Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists