From: Anthony Liguori <anthony@codemonkey.ws>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-devel] Re: Two QMP events issues
Date: Mon, 08 Feb 2010 14:22:34 -0600 [thread overview]
Message-ID: <4B70728A.4000600@codemonkey.ws> (raw)
In-Reply-To: <20100208175943.3ed2bf88@doriath>
On 02/08/2010 01:59 PM, Luiz Capitulino wrote:
>
> Looks reasonable to me, what do think Daniel?
>
> Note that if we agree on the 'context design', I'll have to change
> VNC's events names..
>
Let me give you a few suggestions before diving into it. context might
not be the best name.
For event generated by devices, the event should be raised with
something like qdev_event(&s->dev, QMPEV_WD_EXPIRED, ...).
The context argument should allow a client to determine which device
raised the event. So it could be a combination of the device's qdev
name and it's id.
For event generated by non-qdev mechanisms, we should try our best to
associate context with that event. For instance, a DISCONNECT event
happens to a particular session. We don't quite have VNC session ids
yet but if we did, it would make sense to include that in the context info.
So my thinking is that we don't just want context to serve as a
classification mechanism, but we want it to indicate what
subsystem/device/session generated the event.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-02-08 20:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 13:41 [Qemu-devel] Two QMP events issues Luiz Capitulino
2010-02-08 14:12 ` [Qemu-devel] " Daniel P. Berrange
2010-02-08 14:49 ` Anthony Liguori
2010-02-08 14:56 ` Daniel P. Berrange
2010-02-08 15:13 ` Anthony Liguori
2010-02-08 18:25 ` Luiz Capitulino
2010-02-08 19:14 ` Anthony Liguori
2010-02-08 19:59 ` Luiz Capitulino
2010-02-08 20:22 ` Anthony Liguori [this message]
2010-02-08 18:19 ` Luiz Capitulino
2010-02-09 19:24 ` Jamie Lokier
2010-02-09 19:32 ` Jamie Lokier
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=4B70728A.4000600@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=armbru@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).