From: Anthony Liguori <aliguori@us.ibm.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org, Ryan Harper <ryanh@us.ibm.com>,
kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 0/1] integrate qemu-test into kvm-userspace
Date: Fri, 25 Jul 2008 12:52:20 -0500 [thread overview]
Message-ID: <488A12D4.8010905@us.ibm.com> (raw)
In-Reply-To: <200807251812.34838.paul@codesourcery.com>
Paul Brook wrote:
>> Ultimately, I'd like to push this into qemu since nothing we're doing
>> here is arch or kvm specific.
>>
>
> What advantage does inclusion with qemu give?
> AFAICS You're going to have to download gigabytes of images anyway, so
> wouldn't it make more sense to include the test script with those?
>
The tests themselves are meant to run against pretty much any Linux
image that's configured to use the serial port as a console. The idea
is to be able to run the individual tests with arbitrary QEMU command
lines (think -smp 2 for instance) against arbitrary Linux images. Yeah,
it can't guarantee to be perfect but in practice, it seems to work
pretty well.
Ryan's also included a "make check" framework that assumes a set of
existing images. That may not be useful within QEMU but I think the
tests themselves are.
Regards,
Anthony Liguori
> Paul
>
WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <aliguori@us.ibm.com>
To: Paul Brook <paul@codesourcery.com>
Cc: Ryan Harper <ryanh@us.ibm.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 0/1] integrate qemu-test into kvm-userspace
Date: Fri, 25 Jul 2008 12:52:20 -0500 [thread overview]
Message-ID: <488A12D4.8010905@us.ibm.com> (raw)
In-Reply-To: <200807251812.34838.paul@codesourcery.com>
Paul Brook wrote:
>> Ultimately, I'd like to push this into qemu since nothing we're doing
>> here is arch or kvm specific.
>>
>
> What advantage does inclusion with qemu give?
> AFAICS You're going to have to download gigabytes of images anyway, so
> wouldn't it make more sense to include the test script with those?
>
The tests themselves are meant to run against pretty much any Linux
image that's configured to use the serial port as a console. The idea
is to be able to run the individual tests with arbitrary QEMU command
lines (think -smp 2 for instance) against arbitrary Linux images. Yeah,
it can't guarantee to be perfect but in practice, it seems to work
pretty well.
Ryan's also included a "make check" framework that assumes a set of
existing images. That may not be useful within QEMU but I think the
tests themselves are.
Regards,
Anthony Liguori
> Paul
>
next prev parent reply other threads:[~2008-07-25 17:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 16:53 [PATCH 0/1] integrate qemu-test into kvm-userspace Ryan Harper
2008-07-25 16:53 ` [Qemu-devel] " Ryan Harper
2008-07-25 16:53 ` [PATCH 1/1] " Ryan Harper
2008-07-25 16:53 ` [Qemu-devel] " Ryan Harper
2008-07-25 17:12 ` [Qemu-devel] [PATCH 0/1] " Paul Brook
2008-07-25 17:12 ` Paul Brook
2008-07-25 17:52 ` Anthony Liguori [this message]
2008-07-25 17:52 ` Anthony Liguori
2008-07-25 17:57 ` Ryan Harper
2008-07-25 17:57 ` Ryan Harper
2008-07-29 13:17 ` Avi Kivity
2008-07-29 13:17 ` [Qemu-devel] " Avi Kivity
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=488A12D4.8010905@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=ryanh@us.ibm.com \
/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.