From: Kevin Wolf <kwolf@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, lvivier@redhat.com, pbonzini@redhat.com,
mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH RFC] accel: default to an actually available accelerator
Date: Thu, 7 Sep 2017 10:45:43 +0200 [thread overview]
Message-ID: <20170907084543.GC4461@dhcp-200-186.str.redhat.com> (raw)
In-Reply-To: <20170907102538.15ed780d.cohuck@redhat.com>
Am 07.09.2017 um 10:25 hat Cornelia Huck geschrieben:
> On Thu, 7 Sep 2017 10:14:27 +0200
> Thomas Huth <thuth@redhat.com> wrote:
>
> > On 07.09.2017 10:11, Kevin Wolf wrote:
> > [...]
> > > But the real reason why I'm replying: Should we add changing the default
> > > to "kvm:tcg" to the list of planned 3.0 changes? I am part of the group
> > > that intentionally uses TCG occasionally, but I think the majority of
> > > users wants to use KVM (or whatever the fastest option is on their
> > > system) whenever it is available.
> >
> > If you consider how often people are getting this wrong (they want to
> > use KVM but end up with TCG in the first try), I think that's a good idea.
>
> Agreed.
>
> I'm wondering what that means for our tests, though. Some of them work
> slightly different under tcg or kvm (cf. iotest 186, as referenced in
> the original mail), and sometimes you'll probably explicitly want to
> exercise tcg. That does not speak against the change, but we probably
> need to look at what we want in more detail.
This is a bug in test 186, and probably 172, too. Normally, we use the
options from ./common:
export QEMU_OPTIONS="-nodefaults -machine accel=qtest"
However, these two test cases overwrite QEMU_OPTIONS and neglect to add
a '-machine accel=qtest' option manually.
Kevin
next prev parent reply other threads:[~2017-09-07 8:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 9:49 [Qemu-devel] [PATCH RFC] accel: default to an actually available accelerator Cornelia Huck
2017-09-06 11:29 ` Cornelia Huck
2017-09-06 14:35 ` Peter Maydell
2017-09-06 15:54 ` Cornelia Huck
2017-09-11 11:48 ` Paolo Bonzini
2017-09-11 11:51 ` Cornelia Huck
2017-09-11 11:53 ` Paolo Bonzini
2017-09-07 8:11 ` Kevin Wolf
2017-09-07 8:14 ` Thomas Huth
2017-09-07 8:25 ` Cornelia Huck
2017-09-07 8:45 ` Kevin Wolf [this message]
2017-09-11 11:51 ` Paolo Bonzini
2017-09-22 18:15 ` Eduardo Habkost
2017-09-06 14:04 ` Richard Henderson
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=20170907084543.GC4461@dhcp-200-186.str.redhat.com \
--to=kwolf@redhat.com \
--cc=cohuck@redhat.com \
--cc=lvivier@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).