From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: Christoph Egger <Christoph.Egger@amd.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: xen kernel crash at boot since 23598:b24018319772
Date: Fri, 01 Jul 2011 11:18:23 +0100 [thread overview]
Message-ID: <CA335D7F.1D561%keir.xen@gmail.com> (raw)
In-Reply-To: <4E0DB760020000780004B949@nat28.tlf.novell.com>
On 01/07/2011 11:02, "Jan Beulich" <JBeulich@novell.com> wrote:
>>>> On 30.06.11 at 18:33, Keir Fraser <keir.xen@gmail.com> wrote:
>> Note that domain_spin_lock_irq_desc() has a retry loop for a reason! It
>> knows that pirq-irq mapping may change under its feet, so it needs to
>> re-check the mapping with the desc_lock held, at which point the mapping
>> cannot change *if* it obtained the correct desc_lock in time!
>>
>> Perhaps pirq_spin_lock_irq_desc() needs a similar retry loop? Perhaps
>
> Yes. Will send a patch soon.
>
>> pirq_spin_lock_irq_desc() should never have been forked from
>> domain_spin_lock_irq_desc(), and all callers should simply use the former?
>
> I'd rather not - the lookup isn't really inexpensive (and doesn't need
> to be re-done on each iteration either), which is why I created the
> clone in the first place. Instead I think that with adding the retry
> loop here, domain_spin_lock_irq_desc() could become a simple
> wrapper around pirq_spin_lock_irq_desc().
Yes please!
-- Keir
> Jan
>
next prev parent reply other threads:[~2011-07-01 10:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 12:06 xen kernel crash at boot since 23598:b24018319772 Christoph Egger
2011-06-30 12:43 ` Jan Beulich
2011-06-30 14:21 ` Keir Fraser
2011-06-30 15:49 ` Jan Beulich
2011-06-30 16:33 ` Keir Fraser
2011-07-01 10:02 ` Jan Beulich
2011-07-01 10:18 ` Keir Fraser [this message]
2011-06-30 13:23 ` Ian Jackson
2011-06-30 13:29 ` Christoph Egger
2011-06-30 13:48 ` Ian Jackson
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=CA335D7F.1D561%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=Christoph.Egger@amd.com \
--cc=Ian.Jackson@eu.citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.