From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: liang yan <lyan@suse.com>,
Jailhouse <jailhouse-dev@googlegroups.com>,
Claudio Fontana <claudio.fontana@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>,
Hannes Reinecke <hare@suse.de>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [RFC][PATCH 2/3] docs/specs: Add specification of ivshmem device revision 2
Date: Mon, 11 Nov 2019 10:08:20 -0500 [thread overview]
Message-ID: <20191111100607-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <0b0475c1-2564-f433-46d8-ff1a06c13569@siemens.com>
On Mon, Nov 11, 2019 at 02:59:07PM +0100, Jan Kiszka wrote:
> On 11.11.19 14:45, Michael S. Tsirkin wrote:
> > On Mon, Nov 11, 2019 at 01:57:11PM +0100, Jan Kiszka wrote:
> > > +| Offset | Register | Content |
> > > +|-------:|:-----------------------|:-----------------------------------------------------|
> > > +| 00h | Vendor ID | 1AF4h |
> > > +| 02h | Device ID | 1110h |
> >
> > Given it's a virtio vendor ID, please reserve a device ID
> > with the virtio TC.
>
> Yeah, QEMU's IVSHMEM was always using that. I'm happy to make this finally
> official.
>
> Jan
And I guess we will just mark it reserved or something right?
Since at least IVSHMEM 1 isn't a virtio device.
And will you be reusing same ID for IVSHMEM 2 or a new one?
>
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-11-11 15:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 12:57 [RFC][PATCH 0/3] IVSHMEM version 2 device for QEMU Jan Kiszka
2019-11-11 12:57 ` [RFC][PATCH 1/3] hw/misc: Add implementation of ivshmem revision 2 device Jan Kiszka
2019-11-11 12:57 ` [RFC][PATCH 2/3] docs/specs: Add specification of ivshmem device revision 2 Jan Kiszka
2019-11-11 13:45 ` Michael S. Tsirkin
2019-11-11 13:59 ` Jan Kiszka
2019-11-11 15:08 ` Michael S. Tsirkin [this message]
2019-11-11 15:27 ` Daniel P. Berrangé
2019-11-11 15:42 ` Jan Kiszka
2019-11-11 16:14 ` Michael S. Tsirkin
2019-11-11 16:25 ` Jan Kiszka
2019-11-11 16:11 ` Michael S. Tsirkin
2019-11-11 16:38 ` Jan Kiszka
2019-11-12 8:04 ` Michael S. Tsirkin
2019-11-20 18:15 ` Jan Kiszka
2019-12-05 11:14 ` Markus Armbruster
2019-12-05 21:29 ` Jan Kiszka
2019-12-06 10:08 ` Markus Armbruster
2019-11-11 12:57 ` [RFC][PATCH 3/3] contrib: Add server for ivshmem " Jan Kiszka
2019-11-12 0:56 ` [RFC][PATCH 0/3] IVSHMEM version 2 device for QEMU no-reply
2019-11-27 15:28 ` Liang Yan
2019-11-27 17:19 ` Jan Kiszka
2019-12-02 6:16 ` Jan Kiszka
[not found] ` <877b0cd9-d1c5-00c9-c4b6-567c67740962@suse.com>
2019-12-03 7:14 ` Jan Kiszka
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=20191111100607-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=armbru@redhat.com \
--cc=claudio.fontana@gmail.com \
--cc=hare@suse.de \
--cc=jailhouse-dev@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=lyan@suse.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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.