From: Cornelia Huck <cohuck@redhat.com>
To: Roman Kagan <rkagan@virtuozzo.com>
Cc: Siwei Liu <loseweigh@gmail.com>,
Venu Busireddy <venu.busireddy@oracle.com>,
si-wei liu <si-wei.liu@oracle.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Marcel Apfelbaum <marcel@redhat.com>,
virtio-dev@lists.oasis-open.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [virtio-dev] Re: [PATCH v3 0/3] Use of unique identifier for pairing virtio and passthrough devices...
Date: Mon, 9 Jul 2018 18:10:11 +0200 [thread overview]
Message-ID: <20180709181011.3edc4193.cohuck@redhat.com> (raw)
In-Reply-To: <20180709131419.GB6271@rkaganb.sw.ru>
On Mon, 9 Jul 2018 16:14:19 +0300
Roman Kagan <rkagan@virtuozzo.com> wrote:
> On Fri, Jul 06, 2018 at 03:54:06PM +0200, Cornelia Huck wrote:
> > If we want to extend that to other device types, we can add the field
> > in their config space; but I'd rather prefer a more generic "host
> > relays config metainformation" approach.
>
> The problem with this approach is that it's too generic and poorly
> scoped. As a result I guess it's likely to take ages to converge.
I'd certainly not want to wait for it for this particular issue;
however, I think there is value in having this (seeing that at least
Open Stack and s390x DPM already make use of such a mechanism.) But we
can still revisit this later on.
(I'm not too sold on branching out to other device types in general,
but there seems to be demand for it.)
>
> See for instance the discussion on including vm config metadata in qcow2
> images: I think it's similar in scope (or the absense thereof).
>
> Roman.
next prev parent reply other threads:[~2018-07-09 16:10 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 22:19 [Qemu-devel] [PATCH v3 0/3] Use of unique identifier for pairing virtio and passthrough devices Venu Busireddy
2018-06-29 22:19 ` [Qemu-devel] [PATCH v3 1/3] Add "Group Identifier" support to virtio devices Venu Busireddy
2018-06-29 22:19 ` [Qemu-devel] [PATCH v3 2/3] Add "Group Identifier" support to Red Hat PCI bridge Venu Busireddy
2018-07-03 3:13 ` [Qemu-devel] [virtio-dev] " Siwei Liu
2018-06-29 22:19 ` [Qemu-devel] [PATCH v3 3/3] Add "Group Identifier" support to Red Hat PCI Express bridge Venu Busireddy
2018-07-07 12:14 ` [Qemu-devel] [virtio-dev] " Marcel Apfelbaum
2018-07-31 15:58 ` Venu Busireddy
2018-07-31 16:03 ` Michael S. Tsirkin
2018-07-31 19:11 ` Marcel Apfelbaum
2018-06-29 22:19 ` [Qemu-devel] [PATCH v3 virtio 1/1] Add "Group Identifier" to virtio PCI capabilities Venu Busireddy
2018-07-02 16:14 ` [Qemu-devel] [PATCH v3 0/3] Use of unique identifier for pairing virtio and passthrough devices Roman Kagan
2018-07-02 21:14 ` si-wei liu
2018-07-03 9:58 ` Roman Kagan
2018-07-03 14:28 ` Venu Busireddy
2018-07-03 14:52 ` [Qemu-devel] [virtio-dev] " Cornelia Huck
2018-07-03 23:31 ` Siwei Liu
2018-07-04 12:15 ` Cornelia Huck
2018-07-06 0:49 ` Siwei Liu
2018-07-06 13:54 ` Cornelia Huck
2018-07-06 15:07 ` Michael S. Tsirkin
2018-07-09 16:20 ` Cornelia Huck
2018-07-06 23:37 ` Siwei Liu
2018-07-09 16:27 ` Cornelia Huck
2018-07-09 13:14 ` Roman Kagan
2018-07-09 16:10 ` Cornelia Huck [this message]
2018-07-03 15:34 ` [Qemu-devel] " Roman Kagan
2018-07-03 22:27 ` si-wei liu
2018-07-09 13:00 ` Roman Kagan
2018-07-09 18:35 ` Michael S. Tsirkin
2018-07-10 1:11 ` si-wei liu
2018-07-10 1:54 ` Michael S. Tsirkin
2018-07-11 0:07 ` [Qemu-devel] [virtio-dev] " Siwei Liu
2018-07-11 9:53 ` Cornelia Huck
2018-07-12 9:37 ` Siwei Liu
2018-07-12 11:31 ` Cornelia Huck
2018-07-12 20:52 ` Siwei Liu
2018-07-12 21:00 ` Michael S. Tsirkin
2018-07-12 22:19 ` Siwei Liu
2018-07-13 1:20 ` Samudrala, Sridhar
2018-07-13 3:28 ` Michael S. Tsirkin
2018-07-13 9:15 ` Cornelia Huck
2018-07-12 19:18 ` Michael S. Tsirkin
2018-07-10 1:58 ` [Qemu-devel] " Michael S. Tsirkin
2018-07-10 18:56 ` [Qemu-devel] [virtio-dev] " Siwei Liu
2018-07-10 2:05 ` [Qemu-devel] " Michael S. Tsirkin
2018-07-04 5:43 ` Michael S. Tsirkin
2018-07-10 2:11 ` Michael S. Tsirkin
2018-07-10 14:28 ` Venu Busireddy
2018-07-12 21:01 ` Michael S. Tsirkin
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=20180709181011.3edc4193.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=loseweigh@gmail.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkagan@virtuozzo.com \
--cc=si-wei.liu@oracle.com \
--cc=venu.busireddy@oracle.com \
--cc=virtio-dev@lists.oasis-open.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).