linux-kernel - Re: [PATCH] x86: Add a Kconfig shortcut for a kvm-bootable kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 14 Apr 2013 12:31:12 +0300
From:	Pekka Enberg <penberg@...nel.org>
To:	Borislav Petkov <bp@...en8.de>
CC:	Ingo Molnar <mingo@...nel.org>, "H. Peter Anvin" <hpa@...or.com>,
	Sasha Levin <levinsasha928@...il.com>,
	Fengguang Wu <fengguang.wu@...el.com>,
	lkml <linux-kernel@...r.kernel.org>, x86-ml <x86@...nel.org>
Subject: Re: [PATCH] x86: Add a Kconfig shortcut for a kvm-bootable kernel

Hello,

On 4/12/13 9:19 PM, Borislav Petkov wrote:
> so I'm currently experimenting with my randconfig build scripts and
> thought that maybe it would be a cool thing to not only do the random
> builds only but also boot-test them in kvm. Which reminded me that we
> have that KVMTOOL_TEST_ENABLE config option in the kvmtool with which we
> can select all the stuff needed to boot the kernel in kvm.
>
> So I copied it. I now have an all.config in the repo with
> CONFIG_KVM_TEST_ENABLE=y in it so that the random builds can have the
> required support.
>
> So what do people think?
>
> It is pretty helpful for such testing; AFAICT Fengguang is doing his
> testing with kvm so he probably could use it too. And regardless, there
> are more and more reasons to boot the kernel in kvm so having a single
> option which selects the needed support makes more sense with time.
>
> And I haven't picked up the 'make kvmconfig' functionality because it
> is not strictly needed (yet) but it wouldn't hurt if we took it because
> someone has a good reason for needing it.

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.

			Pekka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/