Skip to content

RFC virtio-pci: management device

Jason Wang virtio-comment 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest3 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3virtio-pci: introduce device specific MSI-X messages storecontent.tex+73 -00 replies
2/3virtio-pci: PASID supportcontent.tex+54 -00 replies
3/3virtio-pci: introduce the management device capabilitycontent.tex+75 -00 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [virtio-comment] [RFC PATCH 0/3] virtio-pci: management device

Hi all:

As promised, I post this series to demonstrate the possibility of using a transport specific way for implementing the management device. The main motivation is to achieve hyper scalability and flexibility. This is an alternative way of transporting the managed(virtual) device via the admin virtqueue (most of the admin virtqueue commands proposed there were just a duplication of the PCI capability).

The idea is simple, introduce a device selector and try to reuse as much existing virtio-pci capabilities as possible.

In order to make this work, two independent capabilities are introduced. A new capability for storing MSI-X message is introduced for per-device MSI-X configuration for the managed device. PASID capability is also introduced for DMA isolation among the managed devices.

To be simple, I don't propose device MMU interface in this series. It could be added in the future since it's not a must if PASID is supported.

Sending this for early feedback and comments.

Thanks

Jason Wang (3):
virtio-pci: introduce device specific MSI-X messages store
virtio-pci: PASID support
virtio-pci: introduce the management device capability

 content.tex | 202 ++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 202 insertions(+)
Signature · 18 lines
2.24.3 (Apple Git-128)


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: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
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/