Bruce, I'm working on a v2 of my patches and I was curious how would you like to handle the xen kernel fragment.
Should I go back and make a patch suitable for linux-yocto and submit there? Or stage for meta-virtualization and submit again (with signoff and 3.10 support)? Thanks, -Chris On Fri, Aug 30, 2013 at 1:32 AM, Bruce Ashfield <[email protected]>wrote: > On Thu, Aug 29, 2013 at 11:37 PM, Chris Patterson <[email protected]> > wrote: > > --- > > recipes-kernel/linux/linux-yocto/xen.cfg | 53 > ++++++++++++++++++++++++++++++ > > recipes-kernel/linux/linux-yocto/xen.scc | 4 +++ > > 2 files changed, 57 insertions(+) > > create mode 100644 recipes-kernel/linux/linux-yocto/xen.cfg > > create mode 100644 recipes-kernel/linux/linux-yocto/xen.scc > > > > diff --git a/recipes-kernel/linux/linux-yocto/xen.cfg > b/recipes-kernel/linux/linux-yocto/xen.cfg > > new file mode 100644 > > index 0000000..f9cfb6a > > --- /dev/null > > +++ b/recipes-kernel/linux/linux-yocto/xen.cfg > > Nice. The fragment looks good. I'd actually like to bump this up to the > level of > in-tree support that we have for KVM. > > And by that, I mean that I can merge this to the meta branch of the > linux-yocto > kernel (and also found in the tracking yocto-kernel-cache repository). > > Once there, it can be built and tested standalone, as well as shared by > other > feature fragments. You'd then be able to just enable it via a > KERNEL_FEATURES > entry, just like KVM. > > Cheers, > > Bruce > > > @@ -0,0 +1,53 @@ > > > +.......................................................................... > > +. WARNING > > +. > > +. This file is a kernel configuration fragment, and not a full kernel > > +. configuration file. The final kernel configuration is made up of > > +. an assembly of processed fragments, each of which is designed to > > +. capture a specific part of the final configuration (e.g. platform > > +. configuration, feature configuration, and board specific hardware > > +. configuration). For more information on kernel configuration, please > > +. consult the product documentation. > > +. > > > +.......................................................................... > > + > > +CONFIG_PARAVIRT_GUEST=y > > +# CONFIG_PARAVIRT_TIME_ACCOUNTING is not set > > +CONFIG_XEN=y > > +CONFIG_XEN_DOM0=y > > +CONFIG_XEN_PRIVILEGED_GUEST=y > > +CONFIG_XEN_PVHVM=y > > +CONFIG_XEN_MAX_DOMAIN_MEMORY=500 > > +CONFIG_XEN_SAVE_RESTORE=y > > +# CONFIG_XEN_DEBUG_FS is not set > > +CONFIG_PARAVIRT=y > > +# CONFIG_PARAVIRT_SPINLOCKS is not set > > +CONFIG_PARAVIRT_CLOCK=y > > +# CONFIG_PARAVIRT_DEBUG is not set > > +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_XEN_WDT=m > > +CONFIG_XEN_FBDEV_FRONTEND=y > > +# Xen driver support > > +CONFIG_XEN_BALLOON=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=y > > +CONFIG_XEN_PRIVCMD=m > > +CONFIG_XEN_ACPI_PROCESSOR=m > > +CONFIG_PCI_STUB=y > > diff --git a/recipes-kernel/linux/linux-yocto/xen.scc > b/recipes-kernel/linux/linux-yocto/xen.scc > > new file mode 100644 > > index 0000000..6c68bda > > --- /dev/null > > +++ b/recipes-kernel/linux/linux-yocto/xen.scc > > @@ -0,0 +1,4 @@ > > +define KFEATURE_DESCRIPTION "Xen Dom0 Support" > > +define KFEATURE_COMPATIBILITY board > > + > > +kconf non-hardware xen.cfg > > -- > > 1.7.10.4 > > > > _______________________________________________ > > meta-virtualization mailing list > > [email protected] > > https://lists.yoctoproject.org/listinfo/meta-virtualization > > > > -- > "Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end" >
_______________________________________________ meta-virtualization mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-virtualization
