All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raymond Danks <ray.danks@se-eng.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: "meta-virtualization@yoctoproject.org"
	<meta-virtualization@yoctoproject.org>
Subject: Re: [PATCH 1/2] linux-yocto: added kernel configuration for KVM
Date: Mon, 07 Jan 2013 11:31:34 -0700	[thread overview]
Message-ID: <50EB1486.4080901@se-eng.com> (raw)
In-Reply-To: <CADkTA4NfJq0e-Kcg99uotS1O5ny0uQw=VVmKV0yxwwoMxqdNuw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4211 bytes --]

On 01/07/2013 11:10 AM, Bruce Ashfield wrote:
>
>
>
> On Mon, Jan 7, 2013 at 12:26 PM, Raymond Danks <ray.danks@se-eng.com 
> <mailto:ray.danks@se-eng.com>> wrote:
>
>     I'm going to show my lack of knowledge in this area, but I know
>     this is going to come up when I push a xen.cfg that I apparently
>     never added.
>
>     Is it possible to do something along the lines of PACKAGE_CONFIG
>     in the linux-yocto.bbappend?  For example, in the libvirt package
>     one can use PACKAGE_CONFIG to construct a "minimal" build of
>     libvirt.  What would be the method for one to do the same in this
>     package?
>
>
> kernel configuration fragment use are controlled via the 
> KERNEL_FEATURES variable, and
> for anything pre-yocto 1.4 that means an in-tree kernel configuration 
> fragment (I'm still pushing
> for the fragments to be maintained in tree, since that allows them to 
> be reused and maintained
> more easily).
>
> KERNEL_FEATURES is managed like any other variable in the system, 
> including updating
> it via optional/dynamic features as we see fit.

Thanks Bruce.  Yes, KERNEL_FEATURES is what I was looking for, I 
believe.  I'm seeing some references and examples for this now.

Ray

>
>
>     Yes, I imagine that worst case there can be a SRC_URI_distro
>     definition that includes only the .scc files required for that
>     "minimal" image build, but it seems like we want to keep away from
>     that as much as possible being that this isn't a distro layer.
>
>
> Typically we do this via a base KERNEL_FEATURES specification in the 
> relevant recipe(s), and
> distros, or other configurations can override/extend it as required.
>
> Cheers,
>
> Buce
>
>     Thanks,
>     Ray
>
>
>     On 01/07/2013 05:08 AM, Mihai Prica wrote:
>
>         Signed-off-by: Mihai Prica <mihai.prica@intel.com
>         <mailto:mihai.prica@intel.com>>
>         ---
>           recipes-kernel/linux/linux-yocto/kvm-enable.scc |    4 ++++
>           recipes-kernel/linux/linux-yocto/kvm.cfg        |    4 ++++
>           recipes-kernel/linux/linux-yocto_3.4.bbappend   |    1 +
>           3 files changed, 9 insertions(+)
>           create mode 100644
>         recipes-kernel/linux/linux-yocto/kvm-enable.scc
>           create mode 100644 recipes-kernel/linux/linux-yocto/kvm.cfg
>
>         diff --git a/recipes-kernel/linux/linux-yocto/kvm-enable.scc
>         b/recipes-kernel/linux/linux-yocto/kvm-enable.scc
>         new file mode 100644
>         index 0000000..0b5f4fc
>         --- /dev/null
>         +++ b/recipes-kernel/linux/linux-yocto/kvm-enable.scc
>         @@ -0,0 +1,4 @@
>         +define KFEATURE_DESCRIPTION "Enable KVM host support"
>         +define KFEATURE_COMPATIBILITY board
>         +
>         +kconf non-hardware kvm.cfg
>         diff --git a/recipes-kernel/linux/linux-yocto/kvm.cfg
>         b/recipes-kernel/linux/linux-yocto/kvm.cfg
>         new file mode 100644
>         index 0000000..0cfcf58
>         --- /dev/null
>         +++ b/recipes-kernel/linux/linux-yocto/kvm.cfg
>         @@ -0,0 +1,4 @@
>         +CONFIG_KVM=y
>         +CONFIG_KVM_INTEL=y
>         +CONFIG_KVM_AMD=y
>         +CONFIG_TUN=y
>         diff --git a/recipes-kernel/linux/linux-yocto_3.4.bbappend
>         b/recipes-kernel/linux/linux-yocto_3.4.bbappend
>         index 5b163ff..71bead2 100644
>         --- a/recipes-kernel/linux/linux-yocto_3.4.bbappend
>         +++ b/recipes-kernel/linux/linux-yocto_3.4.bbappend
>         @@ -4,5 +4,6 @@ SRC_URI += "file://xt-checksum.scc \
>                       file://ebtables.scc \
>                     file://vswitch.scc \
>                     file://lxc.scc \
>         +            file://kvm-enable.scc \
>                     "
>
>
>     _______________________________________________
>     meta-virtualization mailing list
>     meta-virtualization@yoctoproject.org
>     <mailto:meta-virtualization@yoctoproject.org>
>     https://lists.yoctoproject.org/listinfo/meta-virtualization
>
>
>
>
> -- 
> "Thou shalt not follow the NULL pointer, for chaos and madness await 
> thee at its end"


[-- Attachment #2: Type: text/html, Size: 8693 bytes --]

  reply	other threads:[~2013-01-07 18:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-07 12:08 [PATCH 0/2] KVM integration Mihai Prica
2013-01-07 12:08 ` [PATCH 1/2] linux-yocto: added kernel configuration for KVM Mihai Prica
2013-01-07 13:42   ` Bruce Ashfield
2013-01-07 17:26   ` Raymond Danks
2013-01-07 18:10     ` Bruce Ashfield
2013-01-07 18:31       ` Raymond Danks [this message]
2013-01-08 18:45         ` Prica, Mihai
2013-01-09  2:20           ` Lei Yang
2013-01-09  3:44           ` Bruce Ashfield
2013-01-09 19:43             ` Prica, Mihai
2013-01-10  7:32               ` Lei Yang
2013-01-10 13:39                 ` Bruce Ashfield
2013-01-07 12:08 ` [PATCH 2/2] Created new target:kvm-image-minimal Mihai Prica
2013-01-07 13:47   ` Bruce Ashfield
2013-01-07 20:26     ` McClintock Matthew-B29882
2013-01-09 19:57       ` Prica, Mihai
2013-01-11 21:19         ` Bruce Ashfield
2013-01-07 12:14 ` [PATCH 0/2] KVM integration David Nyström

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=50EB1486.4080901@se-eng.com \
    --to=ray.danks@se-eng.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=meta-virtualization@yoctoproject.org \
    /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.