> From: Jason Gunthorpe
> Sent: Thursday, July 3, 2025 9:41 PM
>
> On Thu, Jul 03, 2025 at 06:40:48AM +, Tian, Kevin wrote:
> > > From: Jason Gunthorpe
> > > Sent: Wednesday, June 25, 2025 2:35 AM
> > >
> > > @@ -1583,6 +1583,7 @@ static const struct vfio_device_ops
> > > hisi_acc_vfio_pci_o
On Thu, Jul 03, 2025 at 06:40:48AM +, Tian, Kevin wrote:
> > From: Jason Gunthorpe
> > Sent: Wednesday, June 25, 2025 2:35 AM
> >
> > This was missed during the initial implementation. The VFIO PCI encodes
> > the vf_token inside the device name when opening the device from the
> > group
> >
> From: Jason Gunthorpe
> Sent: Wednesday, June 25, 2025 2:35 AM
>
> This was missed during the initial implementation. The VFIO PCI encodes
> the vf_token inside the device name when opening the device from the
> group
> FD, something like:
>
> ":04:10.0 vf_token=bd8d9d2b-5a5f-4f5a-a211-f
On Tue, Jun 24, 2025 at 02:06:04PM -0600, Alex Williamson wrote:
> > This is used to control access to a VF unless there is co-ordination with
> > the owner of the PF.
> >
> > Since we no longer have a device name pass the token directly though
>
> s/name pass/name, pass/ s/though/through/
Got i
On Tue, 24 Jun 2025 15:34:40 -0300
Jason Gunthorpe wrote:
> This was missed during the initial implementation. The VFIO PCI encodes
> the vf_token inside the device name when opening the device from the group
> FD, something like:
>
> ":04:10.0 vf_token=bd8d9d2b-5a5f-4f5a-a211-f591514ba1f3
This was missed during the initial implementation. The VFIO PCI encodes
the vf_token inside the device name when opening the device from the group
FD, something like:
":04:10.0 vf_token=bd8d9d2b-5a5f-4f5a-a211-f591514ba1f3"
This is used to control access to a VF unless there is co-ordinatio
