xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [xen-unstable test] 6947: regressions - trouble: broken/fail/pass
Date: Mon, 02 May 2011 14:39:19 +0100	[thread overview]
Message-ID: <C9E47297.17170%keir.xen@gmail.com> (raw)
In-Reply-To: <C9E46CB7.17164%keir.xen@gmail.com>

On 02/05/2011 14:14, "Keir Fraser" <keir.xen@gmail.com> 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

  reply	other threads:[~2011-05-02 13:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-01 19:56 [xen-unstable test] 6947: regressions - trouble: broken/fail/pass xen.org
2011-05-01 20:48 ` Keir Fraser
2011-05-02  9:01   ` Jan Beulich
2011-05-02 11:22     ` Keir Fraser
2011-05-02 12:00       ` Jan Beulich
2011-05-02 12:13         ` Keir Fraser
2011-05-02 12:24           ` Jan Beulich
2011-05-02 12:19         ` Keir Fraser
2011-05-02 12:29           ` Jan Beulich
2011-05-02 13:14             ` Keir Fraser
2011-05-02 13:39               ` Keir Fraser [this message]
2011-05-02 14:04               ` Jan Beulich
2011-05-02 15:45                 ` Keir Fraser
2011-05-02 16:36                   ` Dan Magenheimer
2011-05-02 17:07                     ` Keir Fraser
2011-05-03  9:35           ` Jan Beulich
2011-05-03 10:09             ` Keir Fraser
2011-05-03 13:36               ` Jan Beulich
2011-05-03 14:09                 ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C9E47297.17170%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=JBeulich@novell.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).