On Mon, 3 Apr 2017, Julien Grall wrote:
> Hi Stefano,
>
> On 31/03/17 21:24, Stefano Stabellini wrote:
> > On Fri, 31 Mar 2017, Julien Grall wrote:
> > > On 30/03/17 00:47, Stefano Stabellini wrote:
> > > > On Fri, 3 Mar 2017, Julien Grall wrote:
> > > What you described is not a data corruption
Hi Stefano,
On 31/03/17 21:24, Stefano Stabellini wrote:
On Fri, 31 Mar 2017, Julien Grall wrote:
On 30/03/17 00:47, Stefano Stabellini wrote:
On Fri, 3 Mar 2017, Julien Grall wrote:
What you described is not a data corruption to me.
No, it is not, thanks to the previous two patches. The
On Fri, 31 Mar 2017, Julien Grall wrote:
> Hi Stefano,
>
> On 30/03/17 00:47, Stefano Stabellini wrote:
> > On Fri, 3 Mar 2017, Julien Grall wrote:
> > > Hi Stefano,
> > >
> > > On 01/03/17 22:15, Stefano Stabellini wrote:
> > > > A potential race condition occurs when vgic_migrate_irq is called
Hi Stefano,
On 30/03/17 00:47, Stefano Stabellini wrote:
On Fri, 3 Mar 2017, Julien Grall wrote:
Hi Stefano,
On 01/03/17 22:15, Stefano Stabellini wrote:
A potential race condition occurs when vgic_migrate_irq is called a
second time, while GIC_IRQ_GUEST_MIGRATING is already set. In that
On Fri, 3 Mar 2017, Julien Grall wrote:
> Hi Stefano,
>
> On 01/03/17 22:15, Stefano Stabellini wrote:
> > A potential race condition occurs when vgic_migrate_irq is called a
> > second time, while GIC_IRQ_GUEST_MIGRATING is already set. In that case,
> > vgic_migrate_irq takes a different vgic
Hi Stefano,
On 01/03/17 22:15, Stefano Stabellini wrote:
A potential race condition occurs when vgic_migrate_irq is called a
second time, while GIC_IRQ_GUEST_MIGRATING is already set. In that case,
vgic_migrate_irq takes a different vgic lock from gic_update_one_lr.
Hmmm, vgic_migrate_irq
A potential race condition occurs when vgic_migrate_irq is called a
second time, while GIC_IRQ_GUEST_MIGRATING is already set. In that case,
vgic_migrate_irq takes a different vgic lock from gic_update_one_lr.
vgic_migrate_irq running concurrently with gic_update_one_lr could cause
data
