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

[Xen-devel] Re: lock issue for vpic_irq_negative_edge


  • To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Thu, 29 Mar 2007 08:34:00 +0100
  • Delivery-date: Thu, 29 Mar 2007 00:31:54 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acdxq2rwPOuYrZ93SlCRhY9uMvANXwAKTL/T
  • Thread-topic: lock issue for vpic_irq_negative_edge

On 29/3/07 03:39, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote:

> Hi, Keir,
> vPIC has a private lock, but there's no acquisition in the
> injection 
> path. This should be a potential issue for change on IRR. Then the
> assertion (ASSERT(vpic_is_locked(vpic)) is likely to be failed within
> vpic_irq_negative_edge if debug option is enabled. Is anything
> missing here?

No, there actually isn't a private vPIC lock any more. If you look at the
top of the vpic.c file you'll see that the 'vpic lock' is actually an alias
for the generic irq_lock. This is always acquired by the caller of
vpic_irq_negative_edge().

 -- Keir

> Thanks,
> Kevin



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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