From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, Parav Pandit <parav@nvidia.com>
Cc: "virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"cohuck@redhat.com" <cohuck@redhat.com>,
"david.edmondson@oracle.com" <david.edmondson@oracle.com>,
"sburla@marvell.com" <sburla@marvell.com>,
Yishai Hadas <yishaih@nvidia.com>,
Maor Gottlieb <maorg@nvidia.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Shahaf Shuler <shahafs@nvidia.com>
Subject: [virtio-dev] Re: [PATCH v2 0/2] transport-pci: Introduce legacy registers access using AQ
Date: Tue, 16 May 2023 11:37:49 +0800 [thread overview]
Message-ID: <78ade48a-6f5d-8a2d-1524-44340f0154ce@redhat.com> (raw)
In-Reply-To: <20230515140052-mutt-send-email-mst@kernel.org>
在 2023/5/16 02:01, Michael S. Tsirkin 写道:
> On Mon, May 15, 2023 at 06:00:02PM +0000, Parav Pandit wrote:
>>> From: Michael S. Tsirkin <mst@redhat.com>
>>> Sent: Monday, May 15, 2023 1:56 PM
>>>
>>> On Mon, May 15, 2023 at 05:51:05PM +0000, Parav Pandit wrote:
>>>>> From: Michael S. Tsirkin <mst@redhat.com>
>>>>> Sent: Monday, May 15, 2023 1:45 PM
>>>>>
>>>>> On Mon, May 15, 2023 at 03:49:44PM +0000, Parav Pandit wrote:
>>>>>> All legacy interface via AQ.
>>>>>> All modern interface access via PCI or its own transport between
>>>>>> driver and
>>>>> device.
>>>>>
>>>>> I am wondering however about the hypervisor notifications.
>>>>> Generally these are the most problematic aspect here I feel. For
>>>>> example, how does it interact with VIRTIO_F_NOTIF_CONFIG_DATA? And
>>>>> generally, having both guest and host be allowed to access device's BAR
>>> seems problematic.
>>>>> Can we reserve a PF BAR region for these things or is that too expensive?
>>>> VIRTIO_F_NOTIF_CONFIG_DATA is not present for the legacy.
>>> it is not but it just might be required, or it won't be there.
>>>
>> How can it be required if it not part of it?
>> I likely didn't follow your question/comment, can you please explain.
> VIRTIO_F_NOTIF_CONFIG_DATA is there presumably for a reason.
>
>>>> For modern device, guest driver will access the device own BAR directly with
>>> its own config_data anyway.
>>>> Should we reserve a region in the PF BAR for SF/SIOV device?, should device
>>> report which BAR/area to use for the given SF/SIOV device?
>>>> May be yes, those are different discussions with tradeoff to consider during
>>> SIOV discussions. It is not related to VFs.
>>>
>>> For SIOV it's a given. But we can do this for SRIOV: reserve a PF region per VF.
>> Each VF has its own BAR area for driver notifications.
> But it is passed through to guest presumably.
Probably not in the case of VIRTIO_F_NOTIF_CONFIG_DATA. Did you see any
problem if we do mediation here except for some performance penalty?
Thanks
>
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-05-16 3:38 UTC|newest]
Thread overview: 126+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-06 0:01 [virtio-dev] [PATCH v2 0/2] transport-pci: Introduce legacy registers access using AQ Parav Pandit
2023-05-06 0:01 ` [virtio-dev] [PATCH v2 1/2] transport-pci: Introduce legacy registers access commands Parav Pandit
2023-05-17 5:44 ` [virtio-dev] " Michael S. Tsirkin
2023-05-17 19:32 ` [virtio-dev] " Parav Pandit
2023-05-18 19:42 ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-05-18 20:51 ` [virtio-dev] " Parav Pandit
2023-05-19 1:54 ` [virtio-dev] " Jason Wang
2023-05-19 2:04 ` [virtio-dev] " Parav Pandit
2023-05-19 6:06 ` [virtio-dev] " Michael S. Tsirkin
2023-05-19 16:37 ` [virtio-dev] " Parav Pandit
2023-05-21 9:16 ` [virtio-dev] " Michael S. Tsirkin
2023-05-21 13:21 ` [virtio-dev] " Parav Pandit
2023-05-21 14:33 ` [virtio-dev] " Michael S. Tsirkin
2023-05-21 14:44 ` [virtio-dev] " Parav Pandit
2023-05-22 20:07 ` [virtio-dev] " Michael S. Tsirkin
2023-05-22 21:05 ` [virtio-dev] " Parav Pandit
2023-05-22 21:34 ` [virtio-dev] " Michael S. Tsirkin
2023-05-23 17:13 ` [virtio-dev] " Parav Pandit
2023-05-23 18:48 ` [virtio-dev] " Michael S. Tsirkin
2023-05-23 22:22 ` [virtio-dev] " Parav Pandit
2023-05-24 1:17 ` [virtio-dev] " Jason Wang
2023-05-24 10:07 ` Michael S. Tsirkin
2023-05-24 19:18 ` [virtio-dev] " Parav Pandit
2023-05-24 20:12 ` [virtio-dev] " Michael S. Tsirkin
2023-05-24 21:02 ` [virtio-dev] " Parav Pandit
2023-05-22 21:42 ` [virtio-dev] " Michael S. Tsirkin
2023-05-22 0:54 ` Jason Wang
2023-05-22 2:46 ` [virtio-dev] " Parav Pandit
2023-05-22 19:35 ` [virtio-dev] " Michael S. Tsirkin
2023-05-06 0:01 ` [virtio-dev] [PATCH v2 2/2] transport-pci: Add legacy register access conformance section Parav Pandit
2023-05-06 2:31 ` [virtio-dev] Re: [PATCH v2 0/2] transport-pci: Introduce legacy registers access using AQ Jason Wang
2023-05-07 13:44 ` Michael S. Tsirkin
2023-05-08 2:23 ` Jason Wang
2023-05-08 17:07 ` Parav Pandit
2023-05-09 3:44 ` Jason Wang
2023-05-09 3:56 ` [virtio-dev] " Parav Pandit
2023-05-10 3:51 ` [virtio-dev] " Jason Wang
2023-05-10 4:22 ` Jason Wang
2023-05-10 16:07 ` Parav Pandit
2023-05-11 7:20 ` [virtio-dev] Re: [virtio-comment] " Jason Wang
2023-05-11 11:35 ` Michael S. Tsirkin
2023-05-15 5:08 ` Jason Wang
2023-05-15 15:25 ` [virtio-dev] " Parav Pandit
2023-05-10 16:04 ` [virtio-dev] " Parav Pandit
2023-05-11 7:17 ` Jason Wang
2023-05-11 14:31 ` [virtio-dev] " Parav Pandit
2023-05-15 5:12 ` [virtio-dev] Re: [virtio-comment] " Jason Wang
2023-05-15 15:26 ` [virtio-dev] " Parav Pandit
2023-05-10 6:04 ` [virtio-dev] " Michael S. Tsirkin
2023-05-10 7:01 ` Jason Wang
2023-05-10 7:43 ` Michael S. Tsirkin
2023-05-10 16:13 ` Parav Pandit
2023-05-11 7:04 ` Jason Wang
2023-05-11 12:54 ` Michael S. Tsirkin
2023-05-11 13:02 ` [virtio-dev] " Parav Pandit
2023-05-15 7:30 ` [virtio-dev] " Jason Wang
2023-05-15 10:08 ` Michael S. Tsirkin
2023-05-15 14:30 ` [virtio-dev] " Parav Pandit
2023-05-23 18:16 ` [virtio-dev] " Michael S. Tsirkin
2023-05-23 21:32 ` [virtio-dev] " Parav Pandit
2023-05-24 5:56 ` [virtio-dev] " Michael S. Tsirkin
2023-05-24 18:57 ` [virtio-dev] " Parav Pandit
2023-05-24 19:58 ` [virtio-dev] " Michael S. Tsirkin
2023-05-24 20:01 ` [virtio-dev] " Parav Pandit
2023-05-24 20:15 ` [virtio-dev] " Michael S. Tsirkin
2023-05-15 15:59 ` [virtio-dev] " Parav Pandit
2023-05-16 6:21 ` [virtio-dev] " Michael S. Tsirkin
2023-05-16 19:11 ` [virtio-dev] " Parav Pandit
2023-05-16 20:58 ` [virtio-dev] " Michael S. Tsirkin
2023-05-16 21:19 ` [virtio-dev] " Parav Pandit
2023-05-16 21:23 ` [virtio-dev] " Michael S. Tsirkin
2023-05-16 21:30 ` [virtio-dev] " Parav Pandit
2023-05-15 7:13 ` [virtio-dev] " Jason Wang
2023-05-11 13:15 ` [virtio-dev] " Parav Pandit
2023-05-11 13:45 ` [virtio-dev] " Michael S. Tsirkin
2023-05-12 14:03 ` Parav Pandit
2023-05-16 3:54 ` Jason Wang
2023-05-16 19:35 ` [virtio-dev] RE: [virtio-comment] " Parav Pandit
2023-05-16 21:11 ` [virtio-dev] " Michael S. Tsirkin
2023-05-16 21:49 ` [virtio-dev] " Parav Pandit
2023-05-16 21:56 ` [virtio-dev] " Michael S. Tsirkin
2023-05-10 16:11 ` [virtio-dev] " Parav Pandit
2023-05-10 16:16 ` Michael S. Tsirkin
2023-05-10 17:33 ` [virtio-dev] " Parav Pandit
2023-05-10 21:08 ` Parav Pandit
2023-05-10 21:33 ` [virtio-dev] " Michael S. Tsirkin
2023-05-10 21:48 ` [virtio-dev] " Parav Pandit
2023-05-11 7:06 ` [virtio-dev] " Jason Wang
2023-05-11 13:04 ` Michael S. Tsirkin
2023-05-15 5:19 ` Jason Wang
2023-05-15 15:31 ` [virtio-dev] " Parav Pandit
2023-05-11 13:28 ` Parav Pandit
2023-05-11 13:38 ` [virtio-dev] " Michael S. Tsirkin
2023-05-11 16:00 ` [virtio-dev] " Parav Pandit
2023-05-11 20:47 ` Parav Pandit
2023-05-11 20:58 ` [virtio-dev] " Michael S. Tsirkin
2023-05-11 21:03 ` [virtio-dev] " Parav Pandit
2023-05-15 16:55 ` Parav Pandit
2023-05-15 7:10 ` [virtio-dev] " Jason Wang
2023-05-15 15:49 ` [virtio-dev] " Parav Pandit
2023-05-15 17:44 ` [virtio-dev] " Michael S. Tsirkin
2023-05-15 17:51 ` [virtio-dev] " Parav Pandit
2023-05-15 17:56 ` [virtio-dev] " Michael S. Tsirkin
2023-05-15 18:00 ` [virtio-dev] " Parav Pandit
2023-05-15 18:01 ` [virtio-dev] " Michael S. Tsirkin
2023-05-15 18:05 ` [virtio-dev] " Parav Pandit
2023-05-16 3:37 ` Jason Wang [this message]
2023-05-16 3:43 ` [virtio-dev] " Jason Wang
2023-05-16 5:38 ` Michael S. Tsirkin
2023-05-16 3:28 ` Jason Wang
2023-05-16 3:45 ` [virtio-dev] " Parav Pandit
2023-05-16 4:08 ` [virtio-dev] " Jason Wang
2023-05-16 19:29 ` [virtio-dev] " Parav Pandit
2023-05-16 21:09 ` [virtio-dev] " Michael S. Tsirkin
2023-05-16 21:41 ` [virtio-dev] " Parav Pandit
2023-05-16 21:54 ` [virtio-dev] " Michael S. Tsirkin
2023-05-16 4:18 ` Michael S. Tsirkin
2023-05-07 9:04 ` Michael S. Tsirkin
2023-05-08 16:54 ` Parav Pandit
2023-05-15 20:29 ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-05-15 20:56 ` [virtio-dev] " Parav Pandit
2023-05-16 4:32 ` [virtio-dev] " Michael S. Tsirkin
2023-05-16 18:45 ` [virtio-dev] " Parav Pandit
2023-05-16 20:42 ` [virtio-dev] " Michael S. Tsirkin
2023-05-23 6:38 ` [virtio-dev] " Michael S. Tsirkin
2023-05-23 17:28 ` [virtio-dev] " Parav Pandit
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=78ade48a-6f5d-8a2d-1524-44340f0154ce@redhat.com \
--to=jasowang@redhat.com \
--cc=cohuck@redhat.com \
--cc=david.edmondson@oracle.com \
--cc=maorg@nvidia.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=sburla@marvell.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=yishaih@nvidia.com \
/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