From: Borislav Petkov <bp@alien8.de>
To: Pekka Enberg <penberg@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Sasha Levin <levinsasha928@gmail.com>,
Fengguang Wu <fengguang.wu@intel.com>,
lkml <linux-kernel@vger.kernel.org>, x86-ml <x86@kernel.org>,
kvm@vger.kernel.org
Subject: Re: [PATCH] x86: Add a Kconfig shortcut for a kvm-bootable kernel
Date: Tue, 16 Apr 2013 18:18:52 +0200 [thread overview]
Message-ID: <20130416161852.GH5332@pd.tnic> (raw)
In-Reply-To: <20130414110320.GB20547@pd.tnic>
On Sun, Apr 14, 2013 at 01:03:20PM +0200, Borislav Petkov wrote:
> On Sun, Apr 14, 2013 at 12:31:12PM +0300, Pekka Enberg wrote:
> > I obviously support having something like this in mainline. I wonder
> > though if we could just call this "default standalone KVM guest
> > config" instead of emphasizing testing angle.
>
> /me nods agreeingly...
>
> And it should be unter HYPERVISOR_GUEST where the rest of this stuff
> resides. Good point.
Sanity check question:
Why not add the select stuff, i.e. this:
select NET
select NETDEVICES
select PCI
select BLOCK
select BLK_DEV
select NETWORK_FILESYSTEMS
select INET
select EXPERIMENTAL
select TTY
select SERIAL_8250
select SERIAL_8250_CONSOLE
select IP_PNP
select IP_PNP_DHCP
select BINFMT_ELF
select PCI_MSI
select HAVE_ARCH_KGDB
select DEBUG_KERNEL
select KGDB
select KGDB_SERIAL_CONSOLE
select VIRTUALIZATION
select VIRTIO
select VIRTIO_RING
select VIRTIO_PCI
select VIRTIO_BLK
select VIRTIO_CONSOLE
select VIRTIO_NET
select 9P_FS
select NET_9P
select NET_9P_VIRTIO
to the option below which we already have. It is in the same sense a KVM
guest support deal.
Hmm.
KVM people, any objections?
config KVM_GUEST
bool "KVM Guest support (including kvmclock)"
depends on PARAVIRT
select PARAVIRT_CLOCK
default y
---help---
This option enables various optimizations for running under the KVM
hypervisor. It includes a paravirtualized clock, so that instead
of relying on a PIT (or probably other) emulation by the
underlying device model, the host provides the guest with
timing infrastructure such as time of day, and system time
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next parent reply other threads:[~2013-04-16 16:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130412181956.GA13099@pd.tnic>
[not found] ` <516A7760.7030907@kernel.org>
[not found] ` <20130414110320.GB20547@pd.tnic>
2013-04-16 16:18 ` Borislav Petkov [this message]
2013-04-17 0:38 ` [PATCH] x86: Add a Kconfig shortcut for a kvm-bootable kernel Sasha Levin
2013-04-17 7:50 ` Borislav Petkov
2013-04-17 23:25 ` Marcelo Tosatti
2013-04-18 9:46 ` Borislav Petkov
2013-04-18 9:55 ` Geert Uytterhoeven
2013-04-18 10:18 ` Borislav Petkov
2013-04-18 13:36 ` Marcelo Tosatti
2013-04-19 10:35 ` Borislav Petkov
2013-04-26 0:05 ` [PATCH -v2] x86: Add a Kconfig shortcut for kvm guest kernel Borislav Petkov
2013-04-26 6:42 ` Ingo Molnar
2013-04-26 9:51 ` [PATCH -v2.1] " Borislav Petkov
2013-05-01 13:19 ` Marcelo Tosatti
2013-05-01 23:21 ` Borislav Petkov
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=20130416161852.GH5332@pd.tnic \
--to=bp@alien8.de \
--cc=fengguang.wu@intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=penberg@kernel.org \
--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