Skip to contentSkip to conversation

content: reserve virtio device ID for QingTian Box devices

PATCH In review Longpeng(Mike) 3 participants 12 messages Dec 9, 2021 – Jan 13, 2022

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 content: reserve virtio device ID for QingTian Box devices

From: Longpeng <[email protected]>

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.

---
 content.tex | 2 ++
 1 file changed, 2 insertions(+)
content.tex +2 -0
index 899df5f..2a6f9de 100644
@@ -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,
Signature · 18 lines
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: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
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/
#1 lore raw

Hi Michael,

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

Quoted 36 lines

-----Original Message-----
From: Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
Sent: Thursday, December 9, 2021 10:06 PM
To: [email protected]
Cc: Gonglei (Arei) <[email protected]>; Longpeng (Mike, Cloud Infrastructure Service Product Dept.) <[email protected]>
Subject: [PATCH] content: reserve virtio device ID for QingTian Box devices

From: Longpeng <[email protected]>

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.

---
 content.tex | 2 ++
 1 file changed, 2 insertions(+)
content.tex +2 -1
index 899df5f..2a6f9de 100644
@@ -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,
--
Quoted 1 line

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: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
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/

#2 lore raw
Quoted 3 lines · Cloud Infrastructure Service Product Dept.)

Hi Michael,

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

Follow these steps please:

https://github.com/oasis-tcs/virtio-spec#use-of-github-issues

Quoted 34 lines
Quoted 34 lines

-----Original Message-----
From: Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
Sent: Thursday, December 9, 2021 10:06 PM
To: [email protected]
Cc: Gonglei (Arei) <[email protected]>; Longpeng (Mike, Cloud Infrastructure Service Product Dept.) <[email protected]>
Subject: [PATCH] content: reserve virtio device ID for QingTian Box devices

From: Longpeng <[email protected]>

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.

---
 content.tex | 2 ++
 1 file changed, 2 insertions(+)
content.tex +2 -0
index 899df5f..2a6f9de 100644
@@ -2893,6 +2893,8 @@ \chapter{Device Types}\label{sec:Device Types}
 \hline
 42         &   RDMA device \\
 \hline
+43         &   QingtianBox \\
+\hline
 \end{tabular}
 
Quoted 3 lines
Quoted 3 lines
content.tex +0 -1
 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: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
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/

#3 lore raw
In reply to Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
Quoted 3 lines · Cloud Infrastructure Service Product Dept.)

Hi Michael,

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

OK, I see the issue was created. I think it makes sense to wait until Jan 3 with the vote since lots of people are on vacation.

Meanwhile - are there plans to add this device to the spec eventually? Can you share a bit more of what it does?

Quoted 34 lines
Quoted 34 lines

-----Original Message-----
From: Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
Sent: Thursday, December 9, 2021 10:06 PM
To: [email protected]
Cc: Gonglei (Arei) <[email protected]>; Longpeng (Mike, Cloud Infrastructure Service Product Dept.) <[email protected]>
Subject: [PATCH] content: reserve virtio device ID for QingTian Box devices

From: Longpeng <[email protected]>

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.

---
 content.tex | 2 ++
 1 file changed, 2 insertions(+)
content.tex +2 -0
index 899df5f..2a6f9de 100644
@@ -2893,6 +2893,8 @@ \chapter{Device Types}\label{sec:Device Types}
 \hline
 42         &   RDMA device \\
 \hline
+43         &   QingtianBox \\
+\hline
 \end{tabular}
 
Quoted 3 lines
Quoted 3 lines
content.tex +0 -1
 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: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
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/

#4 lore raw
Quoted 13 lines

-----Original Message-----
From: Michael S. Tsirkin [mailto:[email protected]]
Sent: Monday, December 27, 2021 4:15 PM
To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.) <[email protected]>
Cc: Gonglei (Arei) <[email protected]>; [email protected]
Subject: Re: [PATCH] content: reserve virtio device ID for QingTian Box devices

On Thu, Dec 23, 2021 at 02:49:25PM +0000, Longpeng (Mike, Cloud Infrastructure Service Product Dept.) wrote:

Quoted 8 lines
Quoted 3 lines

Hi Michael,

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

OK, I see the issue was created. I think it makes sense to wait until Jan 3 with the vote since lots of people are on vacation.

Ok, thanks.

Quoted 3 lines

Meanwhile - are there plans to add this device to the spec eventually? Can you share a bit more of what it does?

We want to carve out some resources (e.g. vcpu, mem, pci_dev) from the user's VM and then use these resources to start a sandbox for the user. The usage quite likes the software enclave which Nitro already supported, but we have much wider usage, for example, running unikernel + app (e.g. OSV + Redis) in the sandbox, it would provide much better performance than the traditional os.

Quoted 34 lines
Quoted 34 lines
Quoted 34 lines

-----Original Message-----
From: Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
Sent: Thursday, December 9, 2021 10:06 PM
To: [email protected]
Cc: Gonglei (Arei) <[email protected]>; Longpeng (Mike, Cloud Infrastructure Service Product Dept.) <[email protected]>
Subject: [PATCH] content: reserve virtio device ID for QingTian Box devices

From: Longpeng <[email protected]>

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.

---
 content.tex | 2 ++
 1 file changed, 2 insertions(+)
content.tex +2 -0
index 899df5f..2a6f9de 100644
@@ -2893,6 +2893,8 @@ \chapter{Device Types}\label{sec:Device Types}
 \hline
 42         &   RDMA device \\
 \hline
+43         &   QingtianBox \\
+\hline
 \end{tabular}
 
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
content.tex +0 -1
 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: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
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/

#5 lore raw
Quoted 26 lines · Cloud Infrastructure Service Product Dept.)
Quoted 11 lines

-----Original Message-----
From: Michael S. Tsirkin [mailto:[email protected]]
Sent: Monday, December 27, 2021 4:15 PM
To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.) <[email protected]>
Cc: Gonglei (Arei) <[email protected]>; [email protected]
Subject: Re: [PATCH] content: reserve virtio device ID for QingTian Box devices

On Thu, Dec 23, 2021 at 02:49:25PM +0000, Longpeng (Mike, Cloud Infrastructure Service Product Dept.) wrote:

Quoted 8 lines
Quoted 3 lines

Hi Michael,

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

OK, I see the issue was created. I think it makes sense to wait until Jan 3 with the vote since lots of people are on vacation.

Ok, thanks.

Quoted 3 lines

Meanwhile - are there plans to add this device to the spec eventually? Can you share a bit more of what it does?

Quoted 5 lines

We want to carve out some resources (e.g. vcpu, mem, pci_dev) from the user's VM and then use these resources to start a sandbox for the user. The usage quite likes the software enclave which Nitro already supported, but we have much wider usage, for example, running unikernel + app (e.g. OSV + Redis) in the sandbox, it would provide much better performance than the traditional os.

Sounds interesting. One question: Should this virtio device only support a specific hypervisor, or could it support various hypervisors in theory? (Via different commands or parameters.) In case of the latter, it might be better to reserve an ID for a "sandbox device" or so. If the design is too closely tied to your hypervisor, I'd be fine with reserving the ID as proposed.

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: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
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/

#6 lore raw
Quoted 48 lines

-----Original Message-----
From: Cornelia Huck [mailto:[email protected]]
Sent: Monday, January 3, 2022 7:30 PM
To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.) <[email protected]>; Michael S. Tsirkin <[email protected]>
Cc: Gonglei (Arei) <[email protected]>; [email protected]
Subject: Re: [virtio-comment] RE: [PATCH] content: reserve virtio device ID for QingTian Box devices

Quoted 26 lines · Cloud Infrastructure Service Product Dept.)
Quoted 11 lines

-----Original Message-----
From: Michael S. Tsirkin [mailto:[email protected]]
Sent: Monday, December 27, 2021 4:15 PM
To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.) <[email protected]>
Cc: Gonglei (Arei) <[email protected]>; [email protected]
Subject: Re: [PATCH] content: reserve virtio device ID for QingTian Box devices

On Thu, Dec 23, 2021 at 02:49:25PM +0000, Longpeng (Mike, Cloud Infrastructure Service Product Dept.) wrote:

Quoted 8 lines
Quoted 3 lines

Hi Michael,

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

OK, I see the issue was created. I think it makes sense to wait until Jan 3 with the vote since lots of people are on vacation.

Ok, thanks.

Quoted 3 lines

Meanwhile - are there plans to add this device to the spec eventually? Can you share a bit more of what it does?

Quoted 6 lines

We want to carve out some resources (e.g. vcpu, mem, pci_dev) from the user's VM and then use these resources to start a sandbox for the user. The usage quite likes the software enclave which Nitro already supported, but we have much wider usage, for example, running unikernel + app (e.g. OSV + Redis) in the sandbox, it would provide much better performance than the traditional os.

Quoted 6 lines

Sounds interesting. One question: Should this virtio device only support a specific hypervisor, or could it support various hypervisors in theory? (Via different commands or parameters.) In case of the latter, it might be better to reserve an ID for a "sandbox device" or so. If the design is too closely tied to your hypervisor, I'd be fine with reserving the ID as proposed.

We want to name the device as "virtio sandbox" originally, but consider that it would be much convenient to add new features (maybe tied to our hypervisor) in the future if we introduce a private device, so we decide to use "QingTian Box" at last.

However, the sandbox function is not bound to a specific hypervisor, so it's free for the other guys to add something like "virtio sandbox".

#7 lore raw
Quoted 53 lines · Cloud Infrastructure Service Product Dept.)
Quoted 46 lines

-----Original Message-----
From: Cornelia Huck [mailto:[email protected]]
Sent: Monday, January 3, 2022 7:30 PM
To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.) <[email protected]>; Michael S. Tsirkin <[email protected]>
Cc: Gonglei (Arei) <[email protected]>; [email protected]
Subject: Re: [virtio-comment] RE: [PATCH] content: reserve virtio device ID for QingTian Box devices

Quoted 26 lines · Cloud Infrastructure Service Product Dept.)
Quoted 11 lines

-----Original Message-----
From: Michael S. Tsirkin [mailto:[email protected]]
Sent: Monday, December 27, 2021 4:15 PM
To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.) <[email protected]>
Cc: Gonglei (Arei) <[email protected]>; [email protected]
Subject: Re: [PATCH] content: reserve virtio device ID for QingTian Box devices

On Thu, Dec 23, 2021 at 02:49:25PM +0000, Longpeng (Mike, Cloud Infrastructure Service Product Dept.) wrote:

Quoted 8 lines
Quoted 3 lines

Hi Michael,

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

OK, I see the issue was created. I think it makes sense to wait until Jan 3 with the vote since lots of people are on vacation.

Ok, thanks.

Quoted 3 lines

Meanwhile - are there plans to add this device to the spec eventually? Can you share a bit more of what it does?

Quoted 6 lines

We want to carve out some resources (e.g. vcpu, mem, pci_dev) from the user's VM and then use these resources to start a sandbox for the user. The usage quite likes the software enclave which Nitro already supported, but we have much wider usage, for example, running unikernel + app (e.g. OSV + Redis) in the sandbox, it would provide much better performance than the traditional os.

Quoted 6 lines

Sounds interesting. One question: Should this virtio device only support a specific hypervisor, or could it support various hypervisors in theory? (Via different commands or parameters.) In case of the latter, it might be better to reserve an ID for a "sandbox device" or so. If the design is too closely tied to your hypervisor, I'd be fine with reserving the ID as proposed.

Quoted 7 lines

We want to name the device as "virtio sandbox" originally, but consider that it would be much convenient to add new features (maybe tied to our hypervisor) in the future if we introduce a private device, so we decide to use "QingTian Box" at last.

However, the sandbox function is not bound to a specific hypervisor, so it's free for the other guys to add something like "virtio sandbox".

Yes, I guess this is a tradeoff between "device for a closely defined environment that can be specified/changed easily" and "generic device covering different environments that gets very complex". I do not have a very good grasp of the problem space; if it is hard to make generic, I have no objection to the specific device id.

Anyone else have a comment? If not, we can go ahead and start a vote.

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: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
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/

#8 lore raw
Quoted 63 lines · Cornelia Huck
Quoted 53 lines · Cloud Infrastructure Service Product Dept.)
Quoted 46 lines

-----Original Message-----
From: Cornelia Huck [mailto:[email protected]]
Sent: Monday, January 3, 2022 7:30 PM
To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.) <[email protected]>; Michael S. Tsirkin <[email protected]>
Cc: Gonglei (Arei) <[email protected]>; [email protected]
Subject: Re: [virtio-comment] RE: [PATCH] content: reserve virtio device ID for QingTian Box devices

Quoted 26 lines · Cloud Infrastructure Service Product Dept.)
Quoted 11 lines

-----Original Message-----
From: Michael S. Tsirkin [mailto:[email protected]]
Sent: Monday, December 27, 2021 4:15 PM
To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.) <[email protected]>
Cc: Gonglei (Arei) <[email protected]>; [email protected]
Subject: Re: [PATCH] content: reserve virtio device ID for QingTian Box devices

On Thu, Dec 23, 2021 at 02:49:25PM +0000, Longpeng (Mike, Cloud Infrastructure Service Product Dept.) wrote:

Quoted 8 lines
Quoted 3 lines

Hi Michael,

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

OK, I see the issue was created. I think it makes sense to wait until Jan 3 with the vote since lots of people are on vacation.

Ok, thanks.

Quoted 3 lines

Meanwhile - are there plans to add this device to the spec eventually? Can you share a bit more of what it does?

Quoted 6 lines

We want to carve out some resources (e.g. vcpu, mem, pci_dev) from the user's VM and then use these resources to start a sandbox for the user. The usage quite likes the software enclave which Nitro already supported, but we have much wider usage, for example, running unikernel + app (e.g. OSV + Redis) in the sandbox, it would provide much better performance than the traditional os.

Quoted 6 lines

Sounds interesting. One question: Should this virtio device only support a specific hypervisor, or could it support various hypervisors in theory? (Via different commands or parameters.) In case of the latter, it might be better to reserve an ID for a "sandbox device" or so. If the design is too closely tied to your hypervisor, I'd be fine with reserving the ID as proposed.

Quoted 7 lines

We want to name the device as "virtio sandbox" originally, but consider that it would be much convenient to add new features (maybe tied to our hypervisor) in the future if we introduce a private device, so we decide to use "QingTian Box" at last.

However, the sandbox function is not bound to a specific hypervisor, so it's free for the other guys to add something like "virtio sandbox".

Quoted 7 lines

Yes, I guess this is a tradeoff between "device for a closely defined environment that can be specified/changed easily" and "generic device covering different environments that gets very complex". I do not have a very good grasp of the problem space; if it is hard to make generic, I have no objection to the specific device id.

Anyone else have a comment? If not, we can go ahead and start a vote.

I'd like to know whether there are plans to add the device to the spec? Driver to linux?

Signature · 18 lines
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: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
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/
#9 lore raw
In reply to Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
Quoted 55 lines · Cloud Infrastructure Service Product Dept.)
Quoted 48 lines

-----Original Message-----
From: Cornelia Huck [mailto:[email protected]]
Sent: Monday, January 3, 2022 7:30 PM
To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.) <[email protected]>; Michael S. Tsirkin <[email protected]>
Cc: Gonglei (Arei) <[email protected]>; [email protected]
Subject: Re: [virtio-comment] RE: [PATCH] content: reserve virtio device ID for QingTian Box devices

Quoted 26 lines · Cloud Infrastructure Service Product Dept.)
Quoted 11 lines

-----Original Message-----
From: Michael S. Tsirkin [mailto:[email protected]]
Sent: Monday, December 27, 2021 4:15 PM
To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.) <[email protected]>
Cc: Gonglei (Arei) <[email protected]>; [email protected]
Subject: Re: [PATCH] content: reserve virtio device ID for QingTian Box devices

On Thu, Dec 23, 2021 at 02:49:25PM +0000, Longpeng (Mike, Cloud Infrastructure Service Product Dept.) wrote:

Quoted 8 lines
Quoted 3 lines

Hi Michael,

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

OK, I see the issue was created. I think it makes sense to wait until Jan 3 with the vote since lots of people are on vacation.

Ok, thanks.

Quoted 3 lines

Meanwhile - are there plans to add this device to the spec eventually? Can you share a bit more of what it does?

Quoted 6 lines

We want to carve out some resources (e.g. vcpu, mem, pci_dev) from the user's VM and then use these resources to start a sandbox for the user. The usage quite likes the software enclave which Nitro already supported, but we have much wider usage, for example, running unikernel + app (e.g. OSV + Redis) in the sandbox, it would provide much better performance than the traditional os.

Quoted 6 lines

Sounds interesting. One question: Should this virtio device only support a specific hypervisor, or could it support various hypervisors in theory? (Via different commands or parameters.) In case of the latter, it might be better to reserve an ID for a "sandbox device" or so. If the design is too closely tied to your hypervisor, I'd be fine with reserving the ID as proposed.

Quoted 7 lines

We want to name the device as "virtio sandbox" originally, but consider that it would be much convenient to add new features (maybe tied to our hypervisor) in the future if we introduce a private device, so we decide to use "QingTian Box" at last.

However, the sandbox function is not bound to a specific hypervisor, so it's free for the other guys to add something like "virtio sandbox".

Hard to say of course but I'm guessing it's better to give it a generic name. Part of the appeal of virtio is it's hypervisor agnostic, hypervisor specific extensions can always be moved to a separate device.

Signature · 1 line
MST
#10 lore raw
Quoted 80 lines

-----Original Message-----
From: Michael S. Tsirkin [mailto:[email protected]]
Sent: Tuesday, January 4, 2022 1:15 AM
To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.) <[email protected]>
Cc: Cornelia Huck <[email protected]>; Gonglei (Arei) <[email protected]>; [email protected]
Subject: Re: [virtio-comment] RE: [PATCH] content: reserve virtio device ID for QingTian Box devices

Quoted 10 lines · Cloud Infrastructure Service Product Dept.)
Quoted 10 lines

-----Original Message-----
From: Cornelia Huck [mailto:[email protected]]
Sent: Monday, January 3, 2022 7:30 PM
To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.) <[email protected]>; Michael S. Tsirkin <[email protected]>
Cc: Gonglei (Arei) <[email protected]>; [email protected]
Subject: Re: [virtio-comment] RE: [PATCH] content: reserve virtio device

ID for

Quoted 5 lines
Quoted 5 lines

QingTian Box devices

On Mon, Dec 27 2021, "Longpeng (Mike, Cloud Infrastructure Service Product
Dept.)" <[email protected]> wrote:

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines

-----Original Message-----
From: Michael S. Tsirkin [mailto:[email protected]]
Sent: Monday, December 27, 2021 4:15 PM
To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.) <[email protected]>
Cc: Gonglei (Arei) <[email protected]>; [email protected]
Subject: Re: [PATCH] content: reserve virtio device ID for QingTian Box

devices

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

On Thu, Dec 23, 2021 at 02:49:25PM +0000, Longpeng (Mike, Cloud

Infrastructure

Quoted 10 lines
Quoted 10 lines
Quoted 10 lines
Quoted 9 lines
Quoted 3 lines · Service Product Dept.)

Hi Michael,

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

OK, I see the issue was created. I think it makes sense to wait until Jan 3 with the vote since lots of people are on vacation.

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines

Ok, thanks.

Quoted 3 lines

Meanwhile - are there plans to add this device to the spec eventually? Can you share a bit more of what it does?

We want to carve out some resources (e.g. vcpu, mem, pci_dev) from the

user's

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

VM and then use these resources to start a sandbox for the user. The usage quite likes the software enclave which Nitro already supported, but we

have

Quoted 1 line
Quoted 1 line
Quoted 1 line

much wider usage, for example, running unikernel + app (e.g. OSV + Redis)

in

Quoted 11 lines
Quoted 9 lines
Quoted 2 lines

the sandbox, it would provide much better performance than the traditional os.

Sounds interesting. One question: Should this virtio device only support a specific hypervisor, or could it support various hypervisors in theory? (Via different commands or parameters.) In case of the latter, it might be better to reserve an ID for a "sandbox device" or so. If the design is too closely tied to your hypervisor, I'd be fine with reserving the ID as proposed.

We want to name the device as "virtio sandbox" originally, but consider that

it

Quoted 1 line

would be much convenient to add new features (maybe tied to our hypervisor)

in

Quoted 1 line

the future if we introduce a private device, so we decide to use "QingTian

Quoted 8 lines

Box"

Quoted 3 lines

at last.

However, the sandbox function is not bound to a specific hypervisor, so it's

free

Quoted 1 line

for the other guys to add something like "virtio sandbox".

Hard to say of course but I'm guessing it's better to give it a generic

If the device only support the sandbox function, then I think a generic name (e.g. virtio-sandbox) would be fine. But as I said above, we want to extend it as a "toolbox" in the near future, not only the sandbox.

Quoted 3 lines

name. Part of the appeal of virtio is it's hypervisor agnostic, hypervisor specific extensions can always be moved to a separate device.

Yes, but we've already introduced a hypervisor specific device (NSM) now, why it's hard to reserve just one ID for other vendors? So I really hope the TC could give a chance for other vendors to do this, maybe you can limit the IDs that a vendor can reserved.

Thanks.

Quoted 2 lines

--
MST

#11 lore raw
Quoted 82 lines · Cloud Infrastructure Service Product Dept.)
Quoted 82 lines

-----Original Message-----
From: Michael S. Tsirkin [mailto:[email protected]]
Sent: Tuesday, January 4, 2022 1:15 AM
To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.) <[email protected]>
Cc: Cornelia Huck <[email protected]>; Gonglei (Arei) <[email protected]>; [email protected]
Subject: Re: [virtio-comment] RE: [PATCH] content: reserve virtio device ID for QingTian Box devices

Quoted 10 lines · Cloud Infrastructure Service Product Dept.)
Quoted 10 lines

-----Original Message-----
From: Cornelia Huck [mailto:[email protected]]
Sent: Monday, January 3, 2022 7:30 PM
To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.) <[email protected]>; Michael S. Tsirkin <[email protected]>
Cc: Gonglei (Arei) <[email protected]>; [email protected]
Subject: Re: [virtio-comment] RE: [PATCH] content: reserve virtio device

ID for

Quoted 5 lines
Quoted 5 lines

QingTian Box devices

On Mon, Dec 27 2021, "Longpeng (Mike, Cloud Infrastructure Service Product
Dept.)" <[email protected]> wrote:

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines

-----Original Message-----
From: Michael S. Tsirkin [mailto:[email protected]]
Sent: Monday, December 27, 2021 4:15 PM
To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.) <[email protected]>
Cc: Gonglei (Arei) <[email protected]>; [email protected]
Subject: Re: [PATCH] content: reserve virtio device ID for QingTian Box

devices

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

On Thu, Dec 23, 2021 at 02:49:25PM +0000, Longpeng (Mike, Cloud

Infrastructure

Quoted 10 lines
Quoted 10 lines
Quoted 10 lines
Quoted 9 lines
Quoted 3 lines · Service Product Dept.)

Hi Michael,

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

OK, I see the issue was created. I think it makes sense to wait until Jan 3 with the vote since lots of people are on vacation.

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines

Ok, thanks.

Quoted 3 lines

Meanwhile - are there plans to add this device to the spec eventually? Can you share a bit more of what it does?

We want to carve out some resources (e.g. vcpu, mem, pci_dev) from the

user's

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

VM and then use these resources to start a sandbox for the user. The usage quite likes the software enclave which Nitro already supported, but we

have

Quoted 1 line
Quoted 1 line
Quoted 1 line

much wider usage, for example, running unikernel + app (e.g. OSV + Redis)

in

Quoted 11 lines
Quoted 9 lines
Quoted 2 lines

the sandbox, it would provide much better performance than the traditional os.

Sounds interesting. One question: Should this virtio device only support a specific hypervisor, or could it support various hypervisors in theory? (Via different commands or parameters.) In case of the latter, it might be better to reserve an ID for a "sandbox device" or so. If the design is too closely tied to your hypervisor, I'd be fine with reserving the ID as proposed.

We want to name the device as "virtio sandbox" originally, but consider that

it

Quoted 1 line

would be much convenient to add new features (maybe tied to our hypervisor)

in

Quoted 1 line

the future if we introduce a private device, so we decide to use "QingTian

Box"

Quoted 3 lines

at last.

However, the sandbox function is not bound to a specific hypervisor, so it's

Quoted 8 lines
Quoted 4 lines

free

Quoted 1 line

for the other guys to add something like "virtio sandbox".

Hard to say of course but I'm guessing it's better to give it a generic

If the device only support the sandbox function, then I think a generic name (e.g. virtio-sandbox) would be fine. But as I said above, we want to extend it as a "toolbox" in the near future, not only the sandbox.

Hm. That would be a vendor-specific toolbox device; I'm not sure whether using that instead of a more generic sandbox device would be a good idea -- I guess we'd end up with duplication for the sandbox functionality. Or does the reset of the toolbox functionality interact with the sandbox functionality?

Quoted 9 lines
Quoted 4 lines

name. Part of the appeal of virtio is it's hypervisor agnostic, hypervisor specific extensions can always be moved to a separate device.

Yes, but we've already introduced a hypervisor specific device (NSM) now, why it's hard to reserve just one ID for other vendors? So I really hope the TC could give a chance for other vendors to do this, maybe you can limit the IDs that a vendor can reserved.

I'm less worried about introducing a hypervisor-specific id and more about introducing something that might be better served by a more generic device with hypervisor-specific subcommands.

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: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
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/