From: "Michael S. Tsirkin" <mst@redhat.com>
To: Vitaly Mireyno <vmireyno@marvell.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Jason Wang <jasowang@redhat.com>,
Ariel Elior <aelior@marvell.com>
Subject: Re: [virtio-comment] [PATCH] virtio-net: Add support for the flexible driver notification
Date: Mon, 3 Feb 2020 04:52:20 -0500 [thread overview]
Message-ID: <20200203044835-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <BN6PR1801MB206715ABAA0A9B46DFED0037C5040@BN6PR1801MB2067.namprd18.prod.outlook.com>
On Thu, Jan 30, 2020 at 04:56:15PM +0000, Vitaly Mireyno wrote:
> The main motivation is to support virtio on the existing
> silicon, where this is the only way. Hopefully more use-cases
> would arise that would find this useful.
So there's some silicon out there that just happened
to use exactly the virtio format, except for a couple
of bits in the notification? Interesting.
And what are these bits actually set to in this hardware? Just curious ...
--
MST
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2020-02-03 9:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 16:56 [virtio-comment] [PATCH] virtio-net: Add support for the flexible driver notification Vitaly Mireyno
2020-02-03 9:52 ` Michael S. Tsirkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-03 11:53 Vitaly Mireyno
2020-01-30 15:53 Vitaly Mireyno
2020-01-30 16:12 ` Michael S. Tsirkin
2020-01-30 12:49 Vitaly Mireyno
2020-01-30 15:07 ` Michael S. Tsirkin
2020-01-28 14:33 Vitaly Mireyno
2020-01-29 9:58 ` Michael S. Tsirkin
2020-01-27 17:00 Vitaly Mireyno
2020-01-27 18:47 ` Michael S. Tsirkin
2020-01-27 12:49 Vitaly Mireyno
2020-01-27 15:34 ` Michael S. Tsirkin
2020-01-26 12:10 Vitaly Mireyno
2020-01-27 9:49 ` Stefan Hajnoczi
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=20200203044835-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=aelior@marvell.com \
--cc=jasowang@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=vmireyno@marvell.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.