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

Re: [Xen-devel] [xen-unstable test] 6947: regressions - trouble: broken/fail/pass

  • To: Jan Beulich <JBeulich@xxxxxxxxxx>
  • From: Keir Fraser <keir.xen@xxxxxxxxx>
  • Date: Mon, 02 May 2011 14:39:19 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 02 May 2011 06:40:24 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=ZBBnu+XY3e+cPbxp9TwItkq4T1shwNNvL71XsHMTYgU8HGQ7cYNzlbuUZP2FIBlYKo /U8okfZQnHq6ziM5Lxlj0KTCTpPe1ayJxvvTWhxIl94l4q3rgrBgfb+FX7p52Ld4KOn8 fmKBZYonL0adwmCHyjDMmKkgLINTsDN2i8XaY=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcwIytXIPAut4LfhEE+Yoia5nR2F7wAA4B0d
  • Thread-topic: [Xen-devel] [xen-unstable test] 6947: regressions - trouble: broken/fail/pass

On 02/05/2011 14:14, "Keir Fraser" <keir.xen@xxxxxxxxx> wrote:

> We'd probably also need an extra lock to protect against concurrent
> radix-tree update operations (should be pretty straightforward to add
> however, needing to protect *only* the radix-tree update calls).

Actually this second lock would need to encompass both the logical and
physical insert/delete operations. Possibly there is already a non-IRQ lock
on these code paths that can contain irq_desc-locked regions. If not then
such a lock would need to be added.

 -- Keir

Xen-devel mailing list



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