[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 31/38] arm: gic.lock can be taken in interrupt context, so lock appropriately.

To: Ian Campbell <ian.campbell@xxxxxxxxxx>
From: Tim Deegan <tim@xxxxxxx>
Date: Thu, 7 Jun 2012 11:20:54 +0100
Cc: xen-devel@xxxxxxxxxxxxx
Delivery-date: Thu, 07 Jun 2012 10:21:10 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

At 15:40 +0000 on 01 Jun (1338565200), Ian Campbell wrote:
> In particular it is taken by gic_set_guest_irq which is called by
> vgic_vcpu_inject_irq
> 
> Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx>

Acked-by: Tim Deegan <tim@xxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

References:
- [Xen-devel] [PATCH 0/38] arm: boot a dom1 to "Calibrating delay loop" then hang
  - From: Ian Campbell
- [Xen-devel] [PATCH 01/38] arm: allocate top level p2m page for all non-idle domains
  - From: Ian Campbell
- [Xen-devel] [PATCH 31/38] arm: gic.lock can be taken in interrupt context, so lock appropriately.
  - From: Ian Campbell

Prev by Date: Re: [Xen-devel] [PATCH 30/38] arm: Upgrade guest barriers to Outer-Shareable. Enable Protected Table Walk.
Next by Date: Re: [Xen-devel] [PATCH 32/38] arm: context switch virtual timer registers
Previous by thread: [Xen-devel] [PATCH 31/38] arm: gic.lock can be taken in interrupt context, so lock appropriately.
Next by thread: Re: [Xen-devel] [PATCH 31/38] arm: gic.lock can be taken in interrupt context, so lock appropriately.
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.