From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Eftime, Petre" <epetre@amazon.com>
Cc: "virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>
Subject: Re: [virtio-comment] Seeking guidance for custom virtIO device
Date: Mon, 13 Apr 2020 07:46:08 -0400 [thread overview]
Message-ID: <20200413074049-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <6774E3D0-4DA4-4CAA-B4D8-370982260E62@amazon.com>
On Fri, Apr 10, 2020 at 09:36:58AM +0000, Eftime, Petre wrote:
> If not, what is the path to having our device live somewhere in the
> virtio world?
Basically submit a spec patch, address review comments, eventually
ask for a TC vote to include it. Reserving an ID is a helpful
first step for many people since that lets you write
guest and host patches.
> If there is no reason to include our device in the spec
> proper, we at least want to reserve an identifier for it, to prevent
> accidental collisions with other devices. I see that there are other
> devices which are rather specialized and not yet formalized listed in
> the spec, but I don't fully graps what steps I need to take in order
> to get an ID. Would submitting a patch with the ID be enough?
Almost.
https://github.com/oasis-tcs/virtio-spec#use-of-github-issues
see text beginning with:
"To request a TC vote on resolving a specific comment:"
https://github.com/oasis-tcs/virtio-spec#providing-feedback
is also helpful.
--
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/
prev parent reply other threads:[~2020-04-13 11:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 9:36 [virtio-comment] Seeking guidance for custom virtIO device Eftime, Petre
2020-04-10 10:09 ` Stefano Garzarella
2020-04-14 10:50 ` Stefan Hajnoczi
2020-04-15 11:23 ` Eftime, Petre
2020-04-17 10:33 ` Stefan Hajnoczi
[not found] ` <15906829-2e85-ed4c-7b06-431d6e856ae9@amazon.de>
2020-04-21 9:37 ` Stefano Garzarella
[not found] ` <a26e9938-49c6-6b63-bb4a-6ba582af3d40@amazon.de>
2020-04-22 8:40 ` Stefano Garzarella
2020-04-29 9:53 ` Stefan Hajnoczi
[not found] ` <fe4a003d-3705-1337-0349-c1c4a0e94125@amazon.de>
2020-04-30 8:43 ` Stefan Hajnoczi
2020-04-29 10:06 ` Stefan Hajnoczi
2020-04-30 8:44 ` Eftime, Petre
2020-04-30 8:59 ` Stefano Garzarella
2020-04-13 11:46 ` Michael S. Tsirkin [this message]
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=20200413074049-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=epetre@amazon.com \
--cc=virtio-comment@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