On March 11, 2016 8:24am, <Tian, Kevin> wrote:
> > From: Xu, Quan
> > Sent: Thursday, March 10, 2016 10:10 PM
> >
> > pcidevs_lock doesn't require interrupts to be disabled while being acquired.
> > However there remains an exception in AMD IOMMU code, where the lock
> > is acquired with interrupt disabled. This inconsistency might lead to 
> > deadlock.
> >
> > The fix is straightforward to use spin_lock instead. Also interrupt
> > has been enabled when this function is invoked, so we're sure
> > consistency around pcidevs_lock can be guaranteed after this fix.
> >
> > Signed-off-by: Quan Xu <quan...@intel.com>
> > Reviewed-by: Dario Faggioli <dario.faggi...@citrix.com>
> > CC: Suravee Suthikulpanit <suravee.suthikulpa...@amd.com>
> > CC: Dario Faggioli <dario.faggi...@citrix.com>
> > CC: Jan Beulich <jbeul...@suse.com>
> > CC: Kevin Tian <kevin.t...@intel.com>
> 
> Reviewed-by: Kevin Tian <kevin.t...@intel.com>

Kevin, thanks!!
Quan

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

Reply via email to