OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

virtio-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [virtio-comment] Re: [PATCH v1 3/8] device-context: Define the device context fields for device migration

> From: Michael S. Tsirkin <mst@redhat.com>
> Sent: Thursday, October 19, 2023 4:50 PM

> > Now, with that, if this can be useful only for non_passthrough, I made humble
> request to transport them using AQ, this way, you get all benefits of AQ.
> > And trying to understand, why AQ cannot possible or inferior?
> I think the real limitation is with the SRIOV group type. If using PASID instead of
> source id for isolation then we'd need a new group type.
RID+PASID is the isolation object.
Havenât seen just PASID.

> And maybe a simpler interface than virtqueue since it's all slow path anyway.
Post functionally working, one will need all features of vq including interrupt notification.

> > If you have commands like suspend/resume device, register or queue
> transport simply donât work, because it's wrong to bifurcate the device with
> such weird API.
> > If you want to biferacate for mediation software, it probably makes sense to
> operate at each VQ level, config space level. Such are very different commands
> than passthrough.
> > I think vdpa has demonstrated that very well on how to do specific work for
> specific device type. So some of those work can be done using AQ.
> >
> > [1]
> > https://lore.kernel.org/virtio-comment/870ace02-f99c-4582-932f-bd10336
> > 2dae9@intel.com/T/#m37743aa924536d0256d6b3b8e83a11c750f28794

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]