[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121020181425.GA11191@liondog.tnic>
Date: Sat, 20 Oct 2012 20:14:25 +0200
From: Borislav Petkov <bp@...en8.de>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Pekka Enberg <penberg@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...nel.org>, Avi Kivity <avi@...hat.com>,
linux-kernel@...r.kernel.org, Christoph Hellwig <hch@...radead.org>
Subject: Re: [GIT PULL] Linux KVM tool for v3.7-rc0
On Sat, Oct 20, 2012 at 06:04:36PM +1100, Stephen Rothwell wrote:
> So are there any compelling arguments from the proponents, or can
> I remove this from linux-next (and have it removed from the tip
> auto-latest branch)?
FWIW, I gave this a run and I have to say, it works as advertized: I
built it and ran it with the latest kernel and the thing simply boots
the kernel. Even without a disk image - the simplest command is:
$ ./lkvm run --kernel ../../arch/x86/boot/bzImage
and it gets me a shell in the vm after a second.
So the absolute advantage it gives kernel devs is that they can
smoke-test whether their stuff boots in seconds.
This is probably not helpful when enabling specific hw features but
should be pretty helpful for generic arch stuff.
HTH.
--
Regards/Gruss,
Boris.
--
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/
Powered by blists - more mailing lists