From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: (spurious?) lockdep warning on Xen boot
Date: Tue, 17 Feb 2009 11:27:54 -0800 [thread overview]
Message-ID: <499B0FBA.4010006@goop.org> (raw)
In-Reply-To: <1234868345.4744.71.camel@laptop>
Peter Zijlstra wrote:
> Right, so you are saying you started out with IRQs enabled, and the
> above local_irq_restore() would simply be the first irq-op to re-enable
> it and goes splat.
>
Yep.
> In which case your disabled from beginning 'fix' looks like the right
> thing to do.
>
OK.
>> Or perhaps the second warning is real; in which case, where does the
>> problem lie? (I guess another case of being bitten by calling
>> __purge_vmap_area_lazy from interrupt context.)
>>
>
> Looks like a real problem, and yes your suggestion makes sense.
>
OK.
Thanks,
J
prev parent reply other threads:[~2009-02-17 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 22:49 (spurious?) lockdep warning on Xen boot Jeremy Fitzhardinge
2009-02-17 10:59 ` Peter Zijlstra
2009-02-17 19:27 ` Jeremy Fitzhardinge [this message]
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=499B0FBA.4010006@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
/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