From: "Daniel P. Berrange" <berrange@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: "Laurent Vivier" <lvivier@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Stefano Stabellini" <stefano.stabellini@eu.citrix.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] [PATCH 0/2] introduce "accel=best"
Date: Tue, 4 Oct 2016 13:07:28 +0100 [thread overview]
Message-ID: <20161004120728.GH5578@redhat.com> (raw)
In-Reply-To: <20161004120046.yklur3w7i7e7yhm4@kamzik.brq.redhat.com>
On Tue, Oct 04, 2016 at 02:00:46PM +0200, Andrew Jones wrote:
> On Tue, Oct 04, 2016 at 01:30:46PM +0200, Laurent Vivier wrote:
> > This series introduces a new parameter to "accel" to
> > ask to use the best one.
> >
> > This allows to remove ugly "kvm accelerator not found"
> > from the "make check" logs.
> >
> > Laurent Vivier (2):
> > accel: allows to select the "best" accelerator
> > tests: use accel=best instead of accel=kvm:tcg
> >
> > accel.c | 58 ++++++++++++++++++++++++++++++++++++++++--------
> > include/sysemu/accel.h | 1 +
> > kvm-all.c | 1 +
> > qemu-options.hx | 4 +++-
> > qtest.c | 1 +
> > tests/bios-tables-test.c | 2 +-
> > tests/postcopy-test.c | 8 +++----
> > xen-common.c | 1 +
> > 8 files changed, 61 insertions(+), 15 deletions(-)
>
> How about probing the host for KVM in the tests. When it's
> available, then only emit accel=kvm. When it's not (and
> it's OK to fallback to tcg), then emit only accel=tcg.
> That's what we do in kvm-unit-tests.
Arguably unit tests should not have any dependancy on the host hardware,
and should be using accel=tcg exclusively, so that they have stable and
predictable behaviour for all developers. Only functional / integration
tests should have dependancies on host hardware/OS, so where accel=kvm
would be appropriate.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|
next prev parent reply other threads:[~2016-10-04 12:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 11:30 [Qemu-devel] [PATCH 0/2] introduce "accel=best" Laurent Vivier
2016-10-04 11:30 ` [Qemu-devel] [PATCH 1/2] accel: allows to select the "best" accelerator Laurent Vivier
2016-10-04 12:00 ` Daniel P. Berrange
2016-10-04 12:29 ` Laurent Vivier
2016-10-04 12:32 ` Peter Maydell
2016-10-04 12:41 ` Paolo Bonzini
2016-10-04 12:49 ` Thomas Huth
2016-10-04 13:31 ` Daniel P. Berrange
2016-10-04 14:18 ` Thomas Huth
2016-10-04 17:16 ` Paolo Bonzini
2016-10-05 1:13 ` Michael S. Tsirkin
2016-10-05 7:21 ` Paolo Bonzini
2016-10-05 7:00 ` Thomas Huth
2016-10-05 7:48 ` Paolo Bonzini
2016-10-04 11:30 ` [Qemu-devel] [PATCH 2/2] tests: use accel=best instead of accel=kvm:tcg Laurent Vivier
2016-10-09 20:50 ` Michael S. Tsirkin
2016-10-04 11:35 ` [Qemu-devel] [PATCH 0/2] introduce "accel=best" Laurent Vivier
2016-10-04 12:00 ` Andrew Jones
2016-10-04 12:07 ` Daniel P. Berrange [this message]
2016-10-04 12:26 ` Andrew Jones
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=20161004120728.GH5578@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=drjones@redhat.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=thuth@redhat.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.