From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Stefan Hajnoczi" <stefanha@linux.vnet.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Anthony Liguori" <anthony@codemonkey.ws>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] Semantics of DeviceState::realized and BlockDriverState
Date: Tue, 12 Jun 2012 10:07:36 +0200 [thread overview]
Message-ID: <4FD6F8C8.2080001@redhat.com> (raw)
In-Reply-To: <4FD6DD47.7020802@redhat.com>
Am 12.06.2012 08:10, schrieb Paolo Bonzini:
> Il 12/06/2012 00:05, Anthony Liguori ha scritto:
>>
>> opened = true
>> attached = true
>>
>> This means that the device is in-use by something in QEMU. Requests may
>> be in flight as read/write requests are now allowed to be issued.
>>
>> Most properties cannot be changed in this state (presumably).
>
> So this is "realized".
I tend to agree, but it's not quite clear to me. It could also be the
intermediate state, but I guess that in practice that would be less useful.
> Or Object needs to provide support for multiple states, and (static)
> properties can have a bitmap of which states let them be modified.
That would probably be the cleanest solution. Not sure if it's worth the
effort, though.
Kevin
next prev parent reply other threads:[~2012-06-12 8:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 22:05 [Qemu-devel] Semantics of DeviceState::realized and BlockDriverState Anthony Liguori
2012-06-12 0:29 ` Andreas Färber
2012-06-12 1:26 ` Anthony Liguori
2012-06-12 6:10 ` Paolo Bonzini
2012-06-12 8:07 ` Kevin Wolf [this message]
2012-06-12 8:02 ` Kevin Wolf
2012-06-13 12:53 ` Markus Armbruster
2012-06-13 12:55 ` Paolo Bonzini
2012-06-13 13:18 ` Anthony Liguori
2012-06-13 15:44 ` Kevin Wolf
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=4FD6F8C8.2080001@redhat.com \
--to=kwolf@redhat.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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.