From: Anthony Liguori <aliguori@us.ibm.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Andreas Faerber <afaerber@suse.de>
Subject: Re: [Qemu-devel] [RFC PATCH 0/6] chardev: convert to QOM
Date: Wed, 17 Oct 2012 09:44:34 -0500 [thread overview]
Message-ID: <87ehkxtay5.fsf@codemonkey.ws> (raw)
In-Reply-To: <507E675A.3040509@redhat.com>
Gerd Hoffmann <kraxel@redhat.com> writes:
> Hi,
>
>> I think the main decision point here is whether we introduce a separate
>> chardev_add/chardev_del command or just use the qom-create command that has
>> been posted previously.
>
> Do you have a git tree with this series + qom-create to look at and play
> with?
https://github.com/aliguori/qemu/tree/chardev-qom.1
I haven't tried the qom-new command from Markus but I've also included
the -object option that I posted a while ago. That seems to work.
Here's an example command line:
$ x86_64-softmmu/qemu-system-x86_64 \
-object chardev-file,path=foo.txt,label=chr0,id=chr0,realized=on \
-device isa-serial,index=0,chardev=chr0 -hda ~/images/linux.img \
-snapshot -enable-kvm
A couple caveats:
- The label/id duplication is ugly. The need to use label disappears
though once we switch devices over to using links.
- Some error checking is needed to deal with trying to use an unrealized
chardev.
- It may still make sense to have a chardev-add operation but I think
that operation should work in terms of something like qom-new.
Probably with some special casing to fix the container path to
/backends/chardev and also to deal with automatically setting label
based on id. It may make sense to also always set realized explicitly
to 'on' in chardev-add.
Regards,
Anthony Liguori
>
> thanks,
> Gerd
prev parent reply other threads:[~2012-10-17 14:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 19:34 [Qemu-devel] [RFC PATCH 0/6] chardev: convert to QOM Anthony Liguori
2012-10-15 19:34 ` [Qemu-devel] [PATCH 1/6] object: add object_property_add_bool Anthony Liguori
2012-10-16 15:44 ` Andreas Färber
2012-10-23 11:30 ` Markus Armbruster
2012-10-15 19:34 ` [Qemu-devel] [PATCH 2/6] chardev: convert to QOM (shallow pass) Anthony Liguori
2012-10-15 19:34 ` [Qemu-devel] [PATCH 3/6] chardev: create new QOM types for each sub chardev type Anthony Liguori
2012-10-15 19:34 ` [Qemu-devel] [PATCH 4/6] chardev: implement realize Anthony Liguori
2012-10-15 19:34 ` [Qemu-devel] [PATCH 5/6] chardev: switch the easy backends to realize Anthony Liguori
2012-10-15 19:34 ` [Qemu-devel] [PATCH 6/6] chardev: convert file backend " Anthony Liguori
2012-10-16 15:52 ` Paolo Bonzini
2012-10-16 19:44 ` Anthony Liguori
2012-10-17 8:07 ` [Qemu-devel] [RFC PATCH 0/6] chardev: convert to QOM Gerd Hoffmann
2012-10-17 14:44 ` Anthony Liguori [this message]
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=87ehkxtay5.fsf@codemonkey.ws \
--to=aliguori@us.ibm.com \
--cc=afaerber@suse.de \
--cc=kraxel@redhat.com \
--cc=pbonzini@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).