From: "Michael S. Tsirkin" <mst@redhat.com>
To: xiexiangyou <xiexiangyou@huawei.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Is it necessary to add a Monitor event of QEVENT_DEVICE_ADDED
Date: Thu, 3 Apr 2014 14:18:33 +0300 [thread overview]
Message-ID: <20140403111833.GB16914@redhat.com> (raw)
In-Reply-To: <533D23C0.8080408@huawei.com>
On Thu, Apr 03, 2014 at 05:02:56PM +0800, xiexiangyou wrote:
> Hi all,
>
> As we know, when hot-add a device, we don't know whether the device is present in VM from outside(like libvirt).
> However, unplugging device, when complete remove the device, Qemu will generate a Monitor event,QEVENT_DEVICE_DELETED.
> Libvirt can receive the event and do something.
> So is it necessary to add a Monitor event of completing add device such as QEVENT_DEVICE_ADDED.
>
> Regards,
> -xie
I don't know.
We have QEVENT_DEVICE_DELETED so libvirt doesn't do things like reuse
the slot. But what would be the point of QEVENT_DEVICE_ADDED?
--
MST
next prev parent reply other threads:[~2014-04-03 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 9:02 [Qemu-devel] Is it necessary to add a Monitor event of QEVENT_DEVICE_ADDED xiexiangyou
2014-04-03 11:18 ` Michael S. Tsirkin [this message]
2014-04-03 12:13 ` Eric Blake
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=20140403111833.GB16914@redhat.com \
--to=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xiexiangyou@huawei.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 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).