Re: [RFC 12/17] irq: bypass: Extend skeleton for ARM forwarding control

From: Eric Auger
Date: Fri Jul 03 2015 - 13:24:13 EST


On 07/03/2015 07:20 PM, Paolo Bonzini wrote:
>
>
> On 03/07/2015 15:12, Eric Auger wrote:
>>>> Linux IRQ and active should be okay. As to the vfio_device handle, you
>>>> should link it from the vfio_platform_device instead. And for the
>>>> vfio_platform_device, you can link it from the vfio_platform_irq instead.
>> For this last one, I don't think this is achievable since if I store the
>> vfio_platform_irq in the opaque, it matches irqs[i] of
>> vfio_platform_device and I don't have any mean to retrieve "i" when
>> calling container_of.
>
> Right, notice I said "link it":
>
> struct vfio_platform_irq *irq =
> container_of(prod, struct vfio_platform_irq, producer);
> struct vfio_platform_device *vpdev = irq->vpdev;
> struct vfio_device *vdev = vpdev->vdev;
>
> Would this be okay?

Yes that's what I did. I added the vfio_device handle in struct
vfio_platform_irq

Thanks ;-)

Have a nice WE

Eric
>
> Paolo
>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/