All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@gmail.com>
To: Borislav Petkov <bp@alien8.de>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Pekka Enberg <penberg@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>, Avi Kivity <avi@redhat.com>,
	linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: [GIT PULL] Linux KVM tool for v3.7-rc0
Date: Sun, 21 Oct 2012 13:07:31 +1000	[thread overview]
Message-ID: <CAPM=9twcHxUGgYUc27DV1AcYZbzKSbA1Bru8vK1kcWvcG0Jpkw@mail.gmail.com> (raw)
In-Reply-To: <20121020181425.GA11191@liondog.tnic>

On Sun, Oct 21, 2012 at 4:14 AM, Borislav Petkov <bp@alien8.de> wrote:
> 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.

Why couldn't this script just be a wrapper around qemu?

I get the kvm developers developing features that isn't ideal, but for
the quick boot a kernel tests, I don't see why a well maintained qemu
wrapper isn't superior. I hate constructing qemu command lines, but a
script in the kernel repo seems like a good idea.

Dave.

  reply	other threads:[~2012-10-21  3:07 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12 11:34 [GIT PULL] Linux KVM tool for v3.7-rc0 Pekka Enberg
2012-10-12 17:27 ` Christoph Hellwig
2012-10-18 10:03   ` Ingo Molnar
2012-10-18 10:31     ` Pekka Enberg
2012-10-16  2:41 ` Stephen Rothwell
2012-10-16 14:50   ` Linus Torvalds
2012-10-20  7:04     ` Stephen Rothwell
2012-10-20 18:14       ` Borislav Petkov
2012-10-21  3:07         ` Dave Airlie [this message]
2012-10-21  3:46           ` Yinghai Lu
2012-10-21 11:03           ` Christoph Hellwig
2012-10-21 12:59             ` Ingo Molnar
2012-10-21 14:02               ` richard -rw- weinberger
2012-10-21 15:03                 ` Ingo Molnar
2012-10-21 17:15                   ` Borislav Petkov
2012-10-21 17:40                     ` Markus Trippelsdorf
2012-10-21 17:51                       ` Ingo Molnar
2012-10-21 17:54                         ` Markus Trippelsdorf
2012-10-21 18:04                           ` Markus Trippelsdorf
2012-10-21 18:10                             ` Ingo Molnar
2012-10-22  9:26                               ` Avi Kivity
2012-10-21 18:09                           ` Ingo Molnar
2012-10-21 15:39                 ` Pekka Enberg
2012-10-22  9:24                   ` Avi Kivity
2012-10-22 10:16                     ` Gleb Natapov
2012-10-23  2:20                       ` Asias He
2012-10-31 15:05                         ` Gleb Natapov
2012-10-21 11:18           ` Borislav Petkov
2012-10-21 11:29             ` richard -rw- weinberger
2012-10-21 22:16               ` Theodore Ts'o
2012-11-14  5:24       ` Stephen Rothwell
2012-11-14  6:02         ` Theodore Ts'o

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='CAPM=9twcHxUGgYUc27DV1AcYZbzKSbA1Bru8vK1kcWvcG0Jpkw@mail.gmail.com' \
    --to=airlied@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=avi@redhat.com \
    --cc=bp@alien8.de \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=penberg@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.