From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: virtio-comment-return-1695-cohuck=redhat.com@lists.oasis-open.org 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 AEC9E986586 for ; Fri, 29 Jan 2021 10:57:59 +0000 (UTC) Date: Fri, 29 Jan 2021 11:57:37 +0100 From: Cornelia Huck Message-ID: <20210129115737.77ea06c5.cohuck@redhat.com> In-Reply-To: References: <20210125055202.29001-1-jasowang@redhat.com> <20210127035117-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 Subject: [virtio-comment] Re: [PATCH V2] virtio-net: introduce admin control virtqueue Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable To: Jason Wang Cc: "Michael S. Tsirkin" , virtio-comment@lists.oasis-open.org List-ID: On Thu, 28 Jan 2021 10:58:49 +0800 Jason Wang wrote: > On 2021/1/27 =E4=B8=8B=E5=8D=886:59, Michael S. Tsirkin wrote: > > Thus, an idea. How about controlling features instead? > > > > And with that, the interface becomes generic and applicable > > to all devices not just net ... =20 >=20 >=20 > Yes, so I think we probably need more than this e.g I had plan to=20 > introduce a general admin virtqueue which could be use to replace the=20 > transport specific way to configure/probe virtual devices. I think we=20 > can add this new features controlling command via that virtqueue. >=20 > So if this makes sense. I will drop the trust command in this patch and= =20 > let admin cvq go first. Then I can post general admin virtqueue patch. >=20 > Does this make sense? So, you'd introduce a generic admin virtqueue and give individual device types the possibility to use it for device type specific commands? This publicly archived list offers a means to provide input to the=0D OASIS Virtual I/O Device (VIRTIO) TC.=0D =0D In order to verify user consent to the Feedback License terms and=0D to minimize spam in the list archive, subscription is required=0D before posting.=0D =0D Subscribe: virtio-comment-subscribe@lists.oasis-open.org=0D Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org=0D List help: virtio-comment-help@lists.oasis-open.org=0D List archive: https://lists.oasis-open.org/archives/virtio-comment/=0D Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf= =0D List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lis= ts=0D Committee: https://www.oasis-open.org/committees/virtio/=0D Join OASIS: https://www.oasis-open.org/join/