From: Stefan Hajnoczi <stefanha@gmail.com>
To: Amos Kong <akong@redhat.com>
Cc: imammedo@redhat.com, lcapitulino@redhat.com,
qemu-devel@nongnu.org, aliguori@amazon.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH] Revert "virtio_rng: replace custom backend API with UserCreatable.complete() callback"
Date: Tue, 19 Aug 2014 15:47:20 +0100 [thread overview]
Message-ID: <20140819144720.GA13680@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1408119832-4354-1-git-send-email-akong@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]
On Sat, Aug 16, 2014 at 12:23:52AM +0800, Amos Kong wrote:
> This reverts commit 57d3e1b3f52d07d215ed96df946ee01f8d9f9526.
>
> The commit introduced a regression bug, the initialization order of virtio-rng
> backend was changed.
>
> # x86_64-softmmu/qemu-system-x86_64 -monitor stdio -vnc :0 \
> -chardev socket,host=localhost,port=1024,id=chr0 \
> -object rng-egd,chardev=chr0,id=rng0
>
> qemu-system-x86_64: -object rng-egd,chardev=chr0,id=rng0: Device 'chr0' not found
>
> Chardev 'chr0' isn't initialized when we try to open rng backend,
More detail:
The problem is that vl.c:main() calls object_create() on -object before
-chardev options are processed. Moving the object_create() call after
chardev is arbitrary and does not work if a chardev depends on an
-object.
It would have been nice to process command-line options in left-to-right
order instead of grouping them by option type. I doubt we can change
this now since it would break the command-line.
> Conflicts:
> hw/virtio/virtio-rng.c
This shouldn't be here.
I agree with reverting commit 57d3e1b3f52d07d215ed96df946ee01f8d9f9526.
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-08-19 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 16:23 [Qemu-devel] [PATCH] Revert "virtio_rng: replace custom backend API with UserCreatable.complete() callback" Amos Kong
2014-08-19 14:47 ` Stefan Hajnoczi [this message]
2014-08-25 16:07 ` Amos Kong
2014-08-26 11:30 ` Markus Armbruster
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=20140819144720.GA13680@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=afaerber@suse.de \
--cc=akong@redhat.com \
--cc=aliguori@amazon.com \
--cc=imammedo@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.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).