From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 474249861FF for ; Mon, 3 Jan 2022 11:30:10 +0000 (UTC) From: Cornelia Huck In-Reply-To: <2be7836713cc4d06ba24b86d21d18094@huawei.com> References: <20211209140543.1876-1-longpeng2@huawei.com> <20211227031128-mutt-send-email-mst@kernel.org> <2be7836713cc4d06ba24b86d21d18094@huawei.com> Date: Mon, 03 Jan 2022 12:29:51 +0100 Message-ID: <87o84t3vm8.fsf@redhat.com> MIME-Version: 1.0 Subject: Re: [virtio-comment] RE: [PATCH] content: reserve virtio device ID for QingTian Box devices Content-Type: text/plain To: "Longpeng (Mike, Cloud Infrastructure Service Product Dept.)" , "Michael S. Tsirkin" Cc: "Gonglei (Arei)" , "virtio-comment@lists.oasis-open.org" List-ID: On Mon, Dec 27 2021, "Longpeng (Mike, Cloud Infrastructure Service Product Dept.)" wrote: >> -----Original Message----- >> From: Michael S. Tsirkin [mailto:mst@redhat.com] >> Sent: Monday, December 27, 2021 4:15 PM >> To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.) >> >> Cc: Gonglei (Arei) ; >> virtio-comment@lists.oasis-open.org >> 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: >> > 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. > >> 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. 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: 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/