Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: "Longpeng (Mike, Cloud Infrastructure Service Product Dept.)" <longpeng2@huawei.com>
To: "mst@redhat.com" <mst@redhat.com>
Cc: "Gonglei (Arei)" <arei.gonglei@huawei.com>,
	"virtio-comment@lists.oasis-open.org"
	<virtio-comment@lists.oasis-open.org>
Subject: [virtio-comment] RE: [PATCH] content: reserve virtio device ID for QingTian Box devices
Date: Thu, 23 Dec 2021 14:49:25 +0000	[thread overview]
Message-ID: <d09a2b0c1cee4d2180b33c452a42794c@huawei.com> (raw)
In-Reply-To: <20211209140543.1876-1-longpeng2@huawei.com>

Hi Michael,

Is there anything else I need to do to reserve the device id?

> -----Original Message-----
> From: Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
> Sent: Thursday, December 9, 2021 10:06 PM
> To: virtio-comment@lists.oasis-open.org
> Cc: Gonglei (Arei) <arei.gonglei@huawei.com>; Longpeng (Mike, Cloud
> Infrastructure Service Product Dept.) <longpeng2@huawei.com>
> Subject: [PATCH] content: reserve virtio device ID for QingTian Box devices
> 
> From: Longpeng <longpeng2@huawei.com>
> 
> Huawei Cloud is one of the famous public cloud providers, and its
> hypervisor is named QingTian. We plan to support the QingTian Box
> that provides some guest-aware features ( for high performance,
> security, etc. ) in the future, and at least one of them is already
> in development. It needs data transmission based on the Virtio, so
> we want to reserve a device id ( 43 ) for the QingTian Box.
> 
> Signed-off-by: Longpeng <longpeng2@huawei.com>
> ---
>  content.tex | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/content.tex b/content.tex
> index 899df5f..2a6f9de 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -2893,6 +2893,8 @@ \chapter{Device Types}\label{sec:Device Types}
>  \hline
>  42         &   RDMA device \\
>  \hline
> +43         &   QingtianBox \\
> +\hline
>  \end{tabular}
> 
>  Some of the devices above are unspecified by this document,
> --
> 1.8.3.1


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/


  reply	other threads:[~2021-12-23 14:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09 14:05 [virtio-comment] [PATCH] content: reserve virtio device ID for QingTian Box devices Longpeng(Mike)
2021-12-23 14:49 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.) [this message]
2021-12-26  8:18   ` [virtio-comment] " Michael S. Tsirkin
2021-12-27  8:15   ` Michael S. Tsirkin
2021-12-27  9:38     ` [virtio-comment] " Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2022-01-03 11:29       ` Cornelia Huck
2022-01-03 11:55         ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2022-01-03 12:50           ` Cornelia Huck
2022-01-03 15:48             ` Michael S. Tsirkin
2022-01-03 17:14           ` Michael S. Tsirkin
2022-01-04  4:49             ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2022-01-13 12:20               ` Cornelia Huck

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=d09a2b0c1cee4d2180b33c452a42794c@huawei.com \
    --to=longpeng2@huawei.com \
    --cc=arei.gonglei@huawei.com \
    --cc=mst@redhat.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