From: Amos Kong <akong@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH for mst/pci] output nc->name in NIC_RX_FILTER_CHANGED event
Date: Mon, 1 Jul 2013 10:55:28 +0800 [thread overview]
Message-ID: <20130701025528.GB1946@amosk.info> (raw)
In-Reply-To: <87vc51i3ra.fsf@blackfin.pond.sub.org>
On Wed, Jun 26, 2013 at 12:07:53PM +0200, Markus Armbruster wrote:
> Amos Kong <akong@redhat.com> writes:
>
> > On Mon, Jun 24, 2013 at 02:34:59PM +0800, Amos Kong wrote:
> >> netclient 'name' entry in event is useful for management to know
> >> which device is changed. n->netclient_name is not always set.
> >> This patch changes to use nc->name. If we don't assign 'id',
> >> qemu will set a generated name to nc->name.
> >
> >
> > IRC: <mst> akong, what do other events include? name or id?
> >
> > I just checked QMP/qmp-event.txt, they all use 'device name'.
> > (eg: BLOCK_IO_ERROR, DEVICE_DELETED, DEVICE_TRAY_MOVED, BLOCK_JOB_*)
> >
> > If we assign 'id' for -device, device name will be set to id.
> > Otherwise, a generated device name will set to some device.
>
> DEVICE_DELETED uses "device" (the qdev ID) and "path" (the QOM path).
>
> For reasons I don't understand, it sets "path" only when the device has
> no qdev ID. That should be cleaned up.
The path are alwasy set.
example:
(have id)
"path": "/machine/peripheral-anon/vnet0/virtio-backend"
(no id)
"path": "/machine/peripheral-anon/device[0]/virtio-backend"
It's enough to just use path to distinguish the changed device.
So we ignore this patch.
--
Amos.
next prev parent reply other threads:[~2013-07-01 2:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 6:34 [Qemu-devel] [PATCH for mst/pci] output nc->name in NIC_RX_FILTER_CHANGED event Amos Kong
2013-06-26 3:15 ` Amos Kong
2013-06-26 10:07 ` Markus Armbruster
2013-07-01 2:55 ` Amos Kong [this message]
2013-07-01 8:19 ` Markus Armbruster
2013-08-01 13:30 ` Andreas Färber
2013-08-01 14:16 ` Amos Kong
2013-06-26 10:02 ` Markus Armbruster
2013-07-01 2:58 ` Amos Kong
2013-08-01 8:59 ` Michael S. Tsirkin
2013-08-01 11:53 ` Amos Kong
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=20130701025528.GB1946@amosk.info \
--to=akong@redhat.com \
--cc=armbru@redhat.com \
--cc=mst@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).