Hi Stefano,
On 03/01/17 23:30, Stefano Stabellini wrote:
On Wed, 28 Dec 2016, Julien Grall wrote:
On 22/12/16 02:15, Stefano Stabellini wrote:
Always take the vgic lock of the old vcpu. When more than one irq
migration is requested before the first one completes, take the vgic
lock of the
On Wed, 28 Dec 2016, Julien Grall wrote:
> Hi Stefano,
>
> On 22/12/16 02:15, Stefano Stabellini wrote:
> > Always take the vgic lock of the old vcpu. When more than one irq
> > migration is requested before the first one completes, take the vgic
> > lock of the oldest vcpu.
> >
> > Write the
Hi Stefano,
On 22/12/16 02:15, Stefano Stabellini wrote:
Always take the vgic lock of the old vcpu. When more than one irq
migration is requested before the first one completes, take the vgic
lock of the oldest vcpu.
Write the new vcpu id into the rank from vgic_migrate_irq, protected by
the
Always take the vgic lock of the old vcpu. When more than one irq
migration is requested before the first one completes, take the vgic
lock of the oldest vcpu.
Write the new vcpu id into the rank from vgic_migrate_irq, protected by
the oldest vgic vcpu lock.
Use barriers to ensure proper
