From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: From: Cornelia Huck In-Reply-To: References: <20220203075716.11684-1-mgurtovoy@nvidia.com> <20220203075716.11684-2-mgurtovoy@nvidia.com> <20220207052843-mutt-send-email-mst@kernel.org> <20220208014039-mutt-send-email-mst@kernel.org> <878rulv6kq.fsf@redhat.com> <20220208084022-mutt-send-email-mst@kernel.org> <875yppv1z2.fsf@redhat.com> Date: Tue, 08 Feb 2022 16:18:21 +0100 Message-ID: <8735ktv136.fsf@redhat.com> MIME-Version: 1.0 Subject: Re: [virtio-dev] RE: [PATCH v3 1/4] Add virtio Admin virtqueue Content-Type: text/plain To: Parav Pandit , "Michael S. Tsirkin" Cc: Max Gurtovoy , "virtio-comment@lists.oasis-open.org" , "virtio-dev@lists.oasis-open.org" , "jasowang@redhat.com" , Shahaf Shuler , Oren Duer , "stefanha@redhat.com" List-ID: On Tue, Feb 08 2022, Parav Pandit wrote: >> From: Cornelia Huck >> Sent: Tuesday, February 8, 2022 8:29 PM > >> very specific (essentially PCI-specific), we need to at least answer the question >> "how could this work for things that are not PCI?" > Why would one want to execute PCI VF MSI-X configuration command for a non PCI device? Well, that obviously does not make sense! But we also obviously still want to be able to target admin commands in general to non-PCI devices. --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org