lkml.org 
[lkml]   [2015]   [Jul]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC 12/17] irq: bypass: Extend skeleton for ARM forwarding control
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
>



\
 
 \ /
  Last update: 2015-07-03 19:41    [W:0.078 / U:0.008 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site