From: "Emilio G. Cota" <cota@braap.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "Markus Armbruster" <armbru@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Vincent Palatin" <vpalatin@chromium.org>,
qemu-devel@nongnu.org, "Eduardo Habkost" <ehabkost@redhat.com>,
"Alex Benn�e" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v2] Fix the -accel parameter and the documentation for 'hax'
Date: Wed, 7 Jun 2017 16:14:10 -0400 [thread overview]
Message-ID: <20170607201410.GA19037@flamenco> (raw)
In-Reply-To: <87pofpnljd.fsf@dusky.pond.sub.org>
On Thu, May 04, 2017 at 09:11:50 +0200, Markus Armbruster wrote:
> Thomas Huth <thuth@redhat.com> writes:
(snip)
> > STEXI
> > @item -accel @var{name}[,prop=@var{value}[,...]]
> > @findex -accel
> > This is used to enable an accelerator. Depending on the target architecture,
> > -kvm, xen, or tcg can be available. By default, tcg is used. If there is more
> > -than one accelerator specified, the next one is used if the previous one fails
> > -to initialize.
> > +kvm, xen, hax or tcg can be available. By default, tcg is used. If there is
> > +more than one accelerator specified, the next one is used if the previous one
> > +fails to initialize.
> > @table @option
> > @item thread=single|multi
> > Controls number of TCG threads. When the TCG is multi-threaded there will be one
> > diff --git a/vl.c b/vl.c
> > index f46e070..0a1b931 100644
> > --- a/vl.c
> > +++ b/vl.c
> > @@ -3725,26 +3725,21 @@ int main(int argc, char **argv, char **envp)
> > qdev_prop_register_global(&kvm_pit_lost_tick_policy);
> > break;
> > }
> > - case QEMU_OPTION_accel:
> > + case QEMU_OPTION_accel: {
> > + QemuOpts *accel_opts;
>
> Doesn't this shadow the @accel_opts declared in main()'s outermost
> scope?
Yes, it does :( Unfortunately Markus' review slipped through the
cracks and this patch ended up upstream (bde4d9205). It causes
a regression that breaks qemu_tcg_configure(accel_opts)
since now accel_opts is always NULL. That is, in `-accel [..],thread=foo'
foo is ignored.
Emilio
next prev parent reply other threads:[~2017-06-07 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 5:24 [Qemu-devel] [PATCH v2] Fix the -accel parameter and the documentation for 'hax' Thomas Huth
2017-05-04 7:11 ` Markus Armbruster
2017-06-07 20:14 ` Emilio G. Cota [this message]
2017-06-08 4:42 ` Thomas Huth
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=20170607201410.GA19037@flamenco \
--to=cota@braap.org \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=vpalatin@chromium.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;
as well as URLs for NNTP newsgroup(s).