[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [virtio-dev] [PATCH v5 04/10] vhost-user: update shared memory capability
On 17/7/20 12:36 Î.Î., Stefan Hajnoczi wrote:
On Mon, May 18, 2020 at 11:37:15PM +0300, Nikos Dragazis wrote:The virtio vhost-user device has shared memory resources. Therefore, it uses the VIRTIO_PCI_CAP_SHARED_MEMORY_CFG capability to standardize those resources through the PCI Configuration Space. This patch synchronizes the virtio vhost-user device spec with the following shared memory resources PATCH: https://lists.oasis-open.org/archives/virtio-dev/201902/msg00142.html Cc: Dr. David Alan Gilbert <dgilbert@redhat.com> Signed-off-by: Nikos Dragazis <ndragazis@arrikto.com> --- virtio-vhost-user.tex | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/virtio-vhost-user.tex b/virtio-vhost-user.tex index 7a8cd9c..d1305dd 100644 --- a/virtio-vhost-user.tex +++ b/virtio-vhost-user.tex @@ -320,7 +320,22 @@ \subsubsection{Notification structure layout}\label{sec:Device Types / Vhost-use \subsubsection{Shared memory capability}\label{sec:Device Types / Vhost-user Device Backend / Additional Device Resources over PCI / Shared Memory capability}The shared memory location is found using the VIRTIO_PCI_CAP_SHARED_MEMORY_CFGNow that Shared Memory Resources are part of the VIRTIO device model the virtio-vhost-user spec should not refer to PCI-specific details anymore. It should just explain which Shared Memory Resources are available on the device. The mapping to PCI is already covered in the VIRTIO PCI transport spec section.
Right. Actually, I have removed the PCI-specific details in the commit 08/10. I see that having non-incremental commits creates confusion, so I will not be doing this anymore.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]