public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave@sr71.net>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org, bp@suse.de,
	dtor@vmware.com, kys@microsoft.com, haiyangz@microsoft.com,
	agraf@suse.de, gleb@redhat.com
Subject: Re: [PATCH 11/12] x86 Kconfig: create x86/Kconfig.virt
Date: Mon, 13 Jan 2014 16:04:58 -0800	[thread overview]
Message-ID: <52D47F2A.6030609@sr71.net> (raw)
In-Reply-To: <52D472ED.3050303@redhat.com>

On 01/13/2014 03:12 PM, Paolo Bonzini wrote:
> Il 14/01/2014 00:00, Dave Hansen ha scritto:
>>>>         --- Virtualization                                                                          
>>>>         <*>   Kernel-based Virtual Machine (KVM) support                                            
>>>>         <*>     KVM for Intel processors support                                                    
>>>>         <*>     KVM for AMD processors support
>>>>         [*]     Audit KVM MMU                                                                       
>>>>         [*]     KVM legacy PCI device assignment support                                            
>>>>         < >   Host kernel accelerator for virtio net
>>>>         [*]   Linux guest support  --->
> 
> I think this is as confusing as before, perhaps worse because it is not
> clear that Linux guest support is not limited to KVM.

The "Linux guest support" menu is preexisting.  This patch just moves it
verbatim from "Processor type and features" to "Virtualization".  My
logic is that "Linux guest support" has a heck of a lot more to do with
"Virtualization" than the processor.

> If you really
> want a Virtualization menu, you have to clearly separate the guest and host:
> 
>     --- Virtualization
>         Linux guest support  --->
>         Virtualization host support  --->
> 
> with KVM and vhost under the second item.

I think it's kinda silly to have folks chase through two levels of menus
when the submenus would have both fit on the screen anyway.  Let's save
the layers of nesting for when we have 150 items in a menu.

I'll have new patches out in a sec.

  reply	other threads:[~2014-01-14  0:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 19:22 [PATCH 00/12] [v2] Reorganize x86 Kconfig menu Dave Hansen
2014-01-13 19:22 ` [PATCH 01/12] x86 Kconfig: create extended platforms menu Dave Hansen
2014-01-13 19:22 ` [PATCH 02/12] x86 Kconfig: memory options Dave Hansen
2014-01-13 19:22 ` [PATCH 03/12] x86 Kconfig: move highmem Dave Hansen
2014-01-13 19:22 ` [PATCH 04/12] x86 Kconfig: processor options menu Dave Hansen
2014-01-13 19:22 ` [PATCH 05/12] x86 Kconfig: processor drivers Dave Hansen
2014-01-13 19:22 ` [PATCH 06/12] x86 Kconfig: scheduler options Dave Hansen
2014-01-13 19:22 ` [PATCH 07/12] x86 Kconfig: move memtest Dave Hansen
2014-01-13 19:22 ` [PATCH 08/12] x86 Kconfig: bury obscure options Dave Hansen
2014-01-13 19:22 ` [PATCH 09/12] x86 Kconfig: create mtrr menu under processsor options Dave Hansen
2014-01-13 19:22 ` [PATCH 10/12] x86 Kconfig: MCE menu Dave Hansen
2014-01-13 19:22 ` [PATCH 11/12] x86 Kconfig: create x86/Kconfig.virt Dave Hansen
2014-01-13 22:46   ` Paolo Bonzini
2014-01-13 23:00     ` Dave Hansen
2014-01-13 23:12       ` Paolo Bonzini
2014-01-14  0:04         ` Dave Hansen [this message]
2014-01-13 19:23 ` [PATCH 12/12] x86 Kconfig: move paravirt under "Virtualization" Dave Hansen
2014-01-14 14:25 ` [PATCH 00/12] [v2] Reorganize x86 Kconfig menu Borislav Petkov
2014-01-14 22:12   ` Dave Hansen

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=52D47F2A.6030609@sr71.net \
    --to=dave@sr71.net \
    --cc=agraf@suse.de \
    --cc=bp@suse.de \
    --cc=dtor@vmware.com \
    --cc=gleb@redhat.com \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox