From: "Andreas Färber" <afaerber@suse.de>
To: Markus Armbruster <armbru@redhat.com>
Cc: stefanha@redhat.com, qemu-devel@nongnu.org, aliguori@amazon.com,
imammedo@redhat.com, Paolo Bonzini <pbonzini@redhat.com>,
Hani Benhabiles <kroosec@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] qdev: Assign a default device ID when none is provided.
Date: Fri, 10 Jan 2014 10:42:17 +0100 [thread overview]
Message-ID: <52CFC079.9010806@suse.de> (raw)
In-Reply-To: <87iots42zd.fsf@blackfin.pond.sub.org>
Am 10.01.2014 10:09, schrieb Markus Armbruster:
> Commands taking a device ID could be extended to take a path in the QOM
> graph instead of an ID.
>
> In the human monitor, it could perhaps work like this:
>
> IDs consist of letters, digits, '-', '.', '_', starting with a
> letter (see id_wellformed())
>
> If the argument doesn't contain '/', interpret it as ID.
> Else, if it starts with '/', interpret it as QOM path anchored at
> "the root" (which needs to be defined).
> Else, split it at the first '/', and interpret the prefix as ID, and
> the suffix as as QOM path anchored at whatever has that ID.
>
> Requires means to inspect the QOM graph to be usable.
qom-list is available for that purpose today.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-01-10 9:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 19:07 [Qemu-devel] [PATCH] qdev: Assign a default device ID when none is provided Hani Benhabiles
2014-01-08 7:36 ` Markus Armbruster
2014-01-08 17:17 ` Hani Benhabiles
2014-01-08 17:34 ` Paolo Bonzini
2014-01-09 18:18 ` Hani Benhabiles
2014-01-09 18:33 ` Paolo Bonzini
2014-01-10 9:09 ` Markus Armbruster
2014-01-10 9:42 ` Andreas Färber [this message]
2014-01-10 11:54 ` 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=52CFC079.9010806@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=imammedo@redhat.com \
--cc=kroosec@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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.