All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Laurent Vivier" <lvivier@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Michael S . Tsirkin" <mst@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	qemu-devel@nongnu.org,
	"Stefano Stabellini" <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] accel: allows to select the "best" accelerator
Date: Tue, 4 Oct 2016 14:31:14 +0100	[thread overview]
Message-ID: <20161004133114.GL5578@redhat.com> (raw)
In-Reply-To: <912a8fc8-47bd-fffe-60ff-0cd7b006402c@redhat.com>

On Tue, Oct 04, 2016 at 02:49:21PM +0200, Thomas Huth wrote:
> On 04.10.2016 14:41, Paolo Bonzini wrote:
> > 
> > 
> > On 04/10/2016 13:30, Laurent Vivier wrote:
> >> But sometime, user wants to use a real accelerator without knowing
> >> if he really can, with, for instance accel=kvm:tcg.
> >> In this case, and if the accelerator is not available we
> >> have a noisy "XXX accelerator not found".
> >>
> >> By allowing the user to ask the "best" accelerator for the given
> >> target, we can avoid this problem.
> >>
> >> This patch introduces a new parameter for the "accel" property, the
> >> "best" keyword.
> >>
> >> You can ask to use the best accelerator with "-M accel=best",
> >> or if you want to use your favorite accelerator and if it is not
> >> available, the best one, you can use, for instance
> >> "-M accel=kvm:best".
> > 
> > I don't think there's a single definition of a "best" accelerator.  For
> > example, some "-cpu" features may be available only with TCG.  In that
> > case, "kvm:tcg" has a clear meaning ("kvm" if it exists, otherwise
> > "tcg") but "best" doesn't.
> > 
> > I agree with Daniel that unit tests should use "tcg" exclusively, at
> > least as a default.
> 
> Using only tcg has also some disadvantages: For some tests, it's
> interesting to know whether they also work properly with KVM (e.g.
> migration tests), and only using tcg by default slows down the "make
> check" quite a bit - which might become an issue now that we're adding
> more and more tests.

Which tests are you seeing a slow-down for ? make check-unit doesn't
show any difference and for 'make check-qtest' the difference was
negligible (1m47 for KVM vs 1m57 for TCG).  We shouldn't be running
extensive guest workloads in unit tests, so I'd be surprised to see
a major hit in unit test time.

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/ :|

  reply	other threads:[~2016-10-04 13:31 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 [this message]
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
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=20161004133114.GL5578@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --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.