From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH] generalize QOM path resolution
Date: Mon, 30 Jan 2012 16:18:29 +0100 [thread overview]
Message-ID: <4F26B4C5.1080002@redhat.com> (raw)
In-Reply-To: <4F26A924.20900@codemonkey.ws>
On 01/30/2012 03:28 PM, Anthony Liguori wrote:
>>
>> You are not going to have anyway a link<Object>. That makes it fine to
>> resolve a
>> link<Block> and a link<Device> according to different rules.
>
> I think we agreed (in IRC) that we can handle this by changing
> qdev_resolve_path() to take an optional TYPE argument which will cause
> qdev_resolve_path() to only succeed if the resulting object implements
> TYPE.
>
> This can be used to disambiguate partial path matches such that a
> link<BlockDriverState> property would only attempt to do partial path
> resolutions on objects that have BlockDriverState in their parent
> hierarchy.
Yes.
Paolo
prev parent reply other threads:[~2012-01-30 15:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 12:53 [Qemu-devel] [RFC PATCH] generalize QOM path resolution Paolo Bonzini
2012-01-30 13:39 ` Anthony Liguori
2012-01-30 14:03 ` Paolo Bonzini
2012-01-30 14:28 ` Anthony Liguori
2012-01-30 15:18 ` Paolo Bonzini [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=4F26B4C5.1080002@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@codemonkey.ws \
--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).