On Fri, Jul 13, 2012 at 10:54 PM, Myklebust, Trond
<Trond.Myklebust@netapp.com> wrote:
> We could at least make selection of a minimal set of drivers for the
> more common virtualised platforms a lot easier.
> Right now, you need to hunt through 30+ different menus in order to find
> what you need to run in a basic KVM virtual machine...

Yes, every time I build a kernel to be used on KVM I forget something. :-

We could introduce a section in Kconfig which contains selections for
common use cases.
E.g. as Linus requested for minimal distro requirements but also
selections for various common
guest configurations.

--
Thanks,
//richard


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/CAFLxGvxxWodD97=78218wc+tuigAFsNK_PdroDfb4BWTZoxxU w@mail.gmail.com

On Fri, Jul 13, 2012 at 10:54 PM, Myklebust, Trond
<Trond.Myklebust@netapp.com> wrote:
> We could at least make selection of a minimal set of drivers for the
> more common virtualised platforms a lot easier.
> Right now, you need to hunt through 30+ different menus in order to find
> what you need to run in a basic KVM virtual machine...

Yes, every time I build a kernel to be used on KVM I forget something. :-

We could introduce a section in Kconfig which contains selections for
common use cases.
E.g. as Linus requested for minimal distro requirements but also
selections for various common
guest configurations.

--
Thanks,
//richard

--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team

On Fri, Jul 13, 2012 at 11:41:21PM +0200, richard -rw- weinberger wrote:
> On Fri, Jul 13, 2012 at 10:54 PM, Myklebust, Trond
> <Trond.Myklebust@netapp.com> wrote:
> > We could at least make selection of a minimal set of drivers for the
> > more common virtualised platforms a lot easier.
> > Right now, you need to hunt through 30+ different menus in order to find
> > what you need to run in a basic KVM virtual machine...
>
> Yes, every time I build a kernel to be used on KVM I forget something. :-
>
> We could introduce a section in Kconfig which contains selections for
> common use cases.
> E.g. as Linus requested for minimal distro requirements but also
> selections for various common
> guest configurations.

+1.

Same experience with building a kvm kernel so I couldn't agree more.

Thanks.

--
Regards/Gruss,
Boris.


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120714103716.GD26559@liondog.tnic">http://lists.debian.org/20120714103716.GD26559@liondog.tnic

On Fri, Jul 13, 2012 at 11:41:21PM +0200, richard -rw- weinberger wrote:
> On Fri, Jul 13, 2012 at 10:54 PM, Myklebust, Trond
> <Trond.Myklebust@netapp.com> wrote:
> > We could at least make selection of a minimal set of drivers for the
> > more common virtualised platforms a lot easier.
> > Right now, you need to hunt through 30+ different menus in order to find
> > what you need to run in a basic KVM virtual machine...
>
> Yes, every time I build a kernel to be used on KVM I forget something. :-
>
> We could introduce a section in Kconfig which contains selections for
> common use cases.
> E.g. as Linus requested for minimal distro requirements but also
> selections for various common
> guest configurations.

+1.

Same experience with building a kvm kernel so I couldn't agree more.

Thanks.

--
Regards/Gruss,
Boris.

--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team

On Sat, Jul 14, 2012 at 1:37 PM, Borislav Petkov <bp@alien8.de> wrote:
> On Fri, Jul 13, 2012 at 11:41:21PM +0200, richard -rw- weinberger wrote:
>> On Fri, Jul 13, 2012 at 10:54 PM, Myklebust, Trond
>> <Trond.Myklebust@netapp.com> wrote:
>> > We could at least make selection of a minimal set of drivers for the
>> > more common virtualised platforms a lot easier.
>> > Right now, you need to hunt through 30+ different menus in order to find
>> > what you need to run in a basic KVM virtual machine...
>>
>> Yes, every time I build a kernel to be used on KVM I forget something. :-
>>
>> We could introduce a section in Kconfig which contains selections for
>> common use cases.
>> E.g. as Linus requested for minimal distro requirements but also
>> selections for various common
>> guest configurations.
>
> +1.
>
> Same experience with building a kvm kernel so I couldn't agree more.

We have "make kvmconfig" in the KVM tool tree that pretty much does
that automatically. There's nothing tools/kvm specific about it so I
guess you could merge that separately.

Pekka

--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team

On Sat, Jul 14, 2012 at 03:12:05PM +0300, Pekka Enberg wrote:
> On Sat, Jul 14, 2012 at 1:37 PM, Borislav Petkov <bp@alien8.de> wrote:
> > On Fri, Jul 13, 2012 at 11:41:21PM +0200, richard -rw- weinberger wrote:
> >> On Fri, Jul 13, 2012 at 10:54 PM, Myklebust, Trond
> >> <Trond.Myklebust@netapp.com> wrote:
> >> > We could at least make selection of a minimal set of drivers for the
> >> > more common virtualised platforms a lot easier.
> >> > Right now, you need to hunt through 30+ different menus in order to find
> >> > what you need to run in a basic KVM virtual machine...
> >>
> >> Yes, every time I build a kernel to be used on KVM I forget something. :-
> >>
> >> We could introduce a section in Kconfig which contains selections for
> >> common use cases.
> >> E.g. as Linus requested for minimal distro requirements but also
> >> selections for various common
> >> guest configurations.
> >
> > +1.
> >
> > Same experience with building a kvm kernel so I couldn't agree more.
>
> We have "make kvmconfig" in the KVM tool tree that pretty much does
> that automatically. There's nothing tools/kvm specific about it so I
> guess you could merge that separately.

Yup, "make kvmconfig" does things right but I guess a general mechanism
might be preferred here

Look, if (at the moment) I'm going to nconfig and virt. section, I see

Virtualization
Kernel-based Virtual Machine (KVM) support
KVM for Intel processors support
KVM for AMD processors support
Audit KVM MMU
Host kernel accelerator for virtio net (EXPERIMENTAL)

and everytime I'm here I need to remember where to search for
virtio devices I would like to include into config. Though I
expect to see in this secrion everything related to virtualization
and have a way to turn on virtio-ring and etc.

For example to enable "PCI driver for virtio devices" I need to
go to Device Drivers -> Virtio drivers, while I think it would
be great to have everything virt. related in Virtualization
section.

(note, I know how to enable all this and where to lookup for
this entries of course, but I guess for regular users it
would be easier to enable various virt. features if they
are gathered in one place)

Cyrill


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20120714124332.GA4093@moon

On Sat, Jul 14, 2012 at 03:12:05PM +0300, Pekka Enberg wrote:
> On Sat, Jul 14, 2012 at 1:37 PM, Borislav Petkov <bp@alien8.de> wrote:
> > On Fri, Jul 13, 2012 at 11:41:21PM +0200, richard -rw- weinberger wrote:
> >> On Fri, Jul 13, 2012 at 10:54 PM, Myklebust, Trond
> >> <Trond.Myklebust@netapp.com> wrote:
> >> > We could at least make selection of a minimal set of drivers for the
> >> > more common virtualised platforms a lot easier.
> >> > Right now, you need to hunt through 30+ different menus in order to find
> >> > what you need to run in a basic KVM virtual machine...
> >>
> >> Yes, every time I build a kernel to be used on KVM I forget something. :-
> >>
> >> We could introduce a section in Kconfig which contains selections for
> >> common use cases.
> >> E.g. as Linus requested for minimal distro requirements but also
> >> selections for various common
> >> guest configurations.
> >
> > +1.
> >
> > Same experience with building a kvm kernel so I couldn't agree more.
>
> We have "make kvmconfig" in the KVM tool tree that pretty much does
> that automatically. There's nothing tools/kvm specific about it so I
> guess you could merge that separately.

Yup, "make kvmconfig" does things right but I guess a general mechanism
might be preferred here

Look, if (at the moment) I'm going to nconfig and virt. section, I see

Virtualization
Kernel-based Virtual Machine (KVM) support
KVM for Intel processors support
KVM for AMD processors support
Audit KVM MMU
Host kernel accelerator for virtio net (EXPERIMENTAL)

and everytime I'm here I need to remember where to search for
virtio devices I would like to include into config. Though I
expect to see in this secrion everything related to virtualization
and have a way to turn on virtio-ring and etc.

For example to enable "PCI driver for virtio devices" I need to
go to Device Drivers -> Virtio drivers, while I think it would
be great to have everything virt. related in Virtualization
section.

(note, I know how to enable all this and where to lookup for
this entries of course, but I guess for regular users it
would be easier to enable various virt. features if they
are gathered in one place)

Cyrill

--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team

On Sat, Jul 14, 2012 at 04:43:32PM +0400, Cyrill Gorcunov wrote:
> For example to enable "PCI driver for virtio devices" I need to go to
> Device Drivers -> Virtio drivers, while I think it would be great to
> have everything virt. related in Virtualization section.

Actually, we need something more generic than that: everything X-related
should be automatically selected when setting CONFIG_X. And X can be any
subset of configuration options which belong to one feature, be it KVM,
distro-specific stuff, or CPU-vendor specific stuff, or whatever.

I can imagine, for example, that when a user wants to have an
AMD-specific config, it automatically selects CPU_SUP_AMD, X86_MCE_AMD
(for MCE), MICROCODE_AMD (microcode support), AGP_AMD64, EDAC_AMD64 and
a bunch of other AMD-specific features.

This would simplify not only the configuration process but also
Kconfig-related build failures since for your configuration you'll make
sure that required stuff is selected.

What I'm saying is that not only distro-specific configs but also some
sort of hierarchical config options could be defined to automatically
preselect stuff for a specific aspect and save a lot of time when
configuring a new system. Our config options have grown humongous right
about now and we can use the simplification. Of course, you can always
do fine-grained tuning afterwards but it'll save a lot of time, in
general.

Let's have an example: when I have to build upstream on a distro here,
I take the distro config and use it despite that it takes a long time
to build since everything is module - it is still better for me to
wait that one time instead of doing a dozen of trial and errors after
forgetting a config option each time.

Thanks.

--
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120714174827.GA13319@aftab.osrc.amd.com">http://lists.debian.org/20120714174827.GA13319@aftab.osrc.amd.com

On Sat, Jul 14, 2012 at 04:43:32PM +0400, Cyrill Gorcunov wrote:
> For example to enable "PCI driver for virtio devices" I need to go to
> Device Drivers -> Virtio drivers, while I think it would be great to
> have everything virt. related in Virtualization section.

Actually, we need something more generic than that: everything X-related
should be automatically selected when setting CONFIG_X. And X can be any
subset of configuration options which belong to one feature, be it KVM,
distro-specific stuff, or CPU-vendor specific stuff, or whatever.

I can imagine, for example, that when a user wants to have an
AMD-specific config, it automatically selects CPU_SUP_AMD, X86_MCE_AMD
(for MCE), MICROCODE_AMD (microcode support), AGP_AMD64, EDAC_AMD64 and
a bunch of other AMD-specific features.

This would simplify not only the configuration process but also
Kconfig-related build failures since for your configuration you'll make
sure that required stuff is selected.

What I'm saying is that not only distro-specific configs but also some
sort of hierarchical config options could be defined to automatically
preselect stuff for a specific aspect and save a lot of time when
configuring a new system. Our config options have grown humongous right
about now and we can use the simplification. Of course, you can always
do fine-grained tuning afterwards but it'll save a lot of time, in
general.

Let's have an example: when I have to build upstream on a distro here,
I take the distro config and use it despite that it takes a long time
to build since everything is module - it is still better for me to
wait that one time instead of doing a dozen of trial and errors after
forgetting a config option each time.

Thanks.

--
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551

--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team

On Sat, Jul 14, 2012 at 07:48:27PM +0200, Borislav Petkov wrote:
> On Sat, Jul 14, 2012 at 04:43:32PM +0400, Cyrill Gorcunov wrote:
> > For example to enable "PCI driver for virtio devices" I need to go to
> > Device Drivers -> Virtio drivers, while I think it would be great to
> > have everything virt. related in Virtualization section.
>
> Actually, we need something more generic than that: everything X-related
> should be automatically selected when setting CONFIG_X. And X can be any
> subset of configuration options which belong to one feature, be it KVM,
> distro-specific stuff, or CPU-vendor specific stuff, or whatever.
>
> I can imagine, for example, that when a user wants to have an
> AMD-specific config, it automatically selects CPU_SUP_AMD, X86_MCE_AMD
> (for MCE), MICROCODE_AMD (microcode support), AGP_AMD64, EDAC_AMD64 and
> a bunch of other AMD-specific features.

sure, no doubts, it would be great! (I must admit I never looked up into
kconfig parser code so i don't know if this could be achieved easily).

Cyrill

--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team