From: Hollis Blanchard <hollisb@us.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm-ppc@vger.kernel.org, kvm <kvm@vger.kernel.org>
Subject: Re: regression tests? (was Re: [PATCH] kvm-userspace: move x86 specific calls introduced by device assignement to x86 files)
Date: Tue, 04 Nov 2008 09:39:36 -0600 [thread overview]
Message-ID: <1225813176.15410.13.camel@localhost.localdomain> (raw)
In-Reply-To: <4910697E.8020006@redhat.com>
On Tue, 2008-11-04 at 17:25 +0200, Avi Kivity wrote:
> Hollis Blanchard wrote:
> > Avi, do you have a quick regression test you run before pushing new
> > patches? If so, we'd like to help you add PowerPC to that, if only to
> > detect build breaks like this one
>
> I have a fairly slow regression test for x86. I would really like to
> get at least build tests for the other archs. I actually have a ppc box
> I could use for it, just need to set it up in some corner and start testing.
Out of curiosity, do you run the slow x86 tests after every commit?
After every batch of commits? Weekly?
Please let us know if we can help set up the PowerPC stuff; it's pretty
important to us to avoid these sorts of problems in the future. We have
tried to write fairly comprehensive build directions at
http://kvm.qumranet.com/kvmwiki/PowerPC_Source and runtime information
at http://kvm.qumranet.com/kvmwiki/PowerPC_Run .
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2008-11-04 15:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 17:16 [PATCH] kvm-userspace: move x86 specific calls introduced by device assignement to x86 files Ehrhardt Christian
2008-11-03 17:21 ` Hollis Blanchard
2008-11-04 10:11 ` Avi Kivity
2008-11-04 15:18 ` regression tests? (was Re: [PATCH] kvm-userspace: move x86 specific calls introduced by device assignement to x86 files) Hollis Blanchard
2008-11-04 15:25 ` Avi Kivity
2008-11-04 15:39 ` Hollis Blanchard [this message]
2008-11-04 15:55 ` 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=1225813176.15410.13.camel@localhost.localdomain \
--to=hollisb@us.ibm.com \
--cc=avi@redhat.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.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