From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: pt_irq_time_out() dropping d->event_lock before calling pirq_guest_eoi() Date: Fri, 08 Apr 2011 12:29:00 +0100 Message-ID: <4D9F0D9C020000780003A934@vpn.id2.novell.com> References: <4D9F0320020000780003A917@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4D9F0320020000780003A917@vpn.id2.novell.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org >>> On 08.04.11 at 12:44, "Jan Beulich" wrote: > What is the reason for this? irq_desc's lock nests inside d->event_lock, > and not having to drop the lock early would not only allow the two loops > to be folded, but also to call a short cut version of pirq_guest_eoi() > that already obtained the pirq->irq mapping (likely going to be created > when splitting the d->nr_pirqs sized arrays I'm working on currently). Actually, this is the only case where pirq_guest_eoi() gets called without holding d->event_lock, so it rather smells like a mistake; I'll go forward folding the second loop into the first, and only undo if there's an actual reason for how things are currently. Jan