From: Borislav Petkov <bp@suse.de>
To: Dave Hansen <dave@sr71.net>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org, dtor@vmware.com,
kys@microsoft.com, haiyangz@microsoft.com, agraf@suse.de,
gleb@redhat.com, pbonzini@redhat.com
Subject: Re: [PATCH 1/2] x86 Kconfig: create x86/Kconfig.virt
Date: Sat, 15 Sep 2018 15:31:48 +0200 [thread overview]
Message-ID: <20180915133148.GB6833@zn.tnic> (raw)
In-Reply-To: <20140114001138.57304DD0@viggo.jf.intel.com>
On Mon, Jan 13, 2014 at 04:11:38PM -0800, Dave Hansen wrote:
>
> From: Dave Hansen <dave.hansen@linux.intel.com>
>
> Right now, there is a "Enable paravirtualization code" option in
> the "Processor Features" menu, which means Xen. There is also a
> group of host-side paravirtualization options specific to KVM
> under the top-level "Virtualization" menu.
>
> I think it makes a lot of sense to group the host and guest side
> things together, especially since the top-level "Virtualization"
> menu is so sparsely populated.
Whoops, those are 4 years old and look forgotten. The idea still makes
sense though, IMO. You could refresh them, if bored ... :-)
Thx.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
prev parent reply other threads:[~2018-09-15 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 0:11 Dave Hansen
2014-01-14 0:11 ` [PATCH 2/2] x86 Kconfig: move guest-side options under "Virtualization" Dave Hansen
2014-01-14 8:01 ` Paolo Bonzini
2014-01-14 8:01 ` [PATCH 1/2] x86 Kconfig: create x86/Kconfig.virt Paolo Bonzini
2018-09-15 13:31 ` Borislav Petkov [this message]
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=20180915133148.GB6833@zn.tnic \
--to=bp@suse.de \
--cc=agraf@suse.de \
--cc=dave@sr71.net \
--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
all inboxes | Powered by JetHome®