From: David Miller <davem@davemloft.net>
To: fweisbec@gmail.com
Cc: rostedt@goodmis.org, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@elte.hu, acme@redhat.com,
a.p.zijlstra@chello.nl, paulus@samba.org
Subject: Re: Random scheduler/unaligned accesses crashes with perf lock events on sparc 64
Date: Tue, 06 Apr 2010 03:28:50 -0700 (PDT) [thread overview]
Message-ID: <20100406.032850.137831355.davem@davemloft.net> (raw)
In-Reply-To: <20100406101925.GD5147@nowhere>
From: Frederic Weisbecker <fweisbec@gmail.com>
Date: Tue, 6 Apr 2010 12:19:28 +0200
> It means having such interrupt reentrancy is not a problem.
It's not reentrancy.
It's the fact that local_irq_disable() (read it again, it's the
"disable" that re-renables NMIs on sparc64) turns NMIs back on even in
code where we are still trying to figure out how to service the NMI
still.
It's because we implement NMIs on sparc64 by having the performance
counter interrupt come in on the level 15 interrupt, and we run the
entire kernel at level 14 when IRQs are "disabled".
next prev parent reply other threads:[~2010-04-06 10:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 12:18 Frederic Weisbecker
2010-04-04 12:21 ` Frederic Weisbecker
2010-04-05 1:00 ` David Miller
2010-04-05 6:57 ` Frederic Weisbecker
2010-04-05 19:22 ` David Miller
2010-04-05 19:40 ` Frederic Weisbecker
2010-04-05 20:46 ` David Miller
2010-04-06 2:15 ` David Miller
2010-04-06 13:41 ` Steven Rostedt
2010-04-06 17:46 ` David Miller
2010-04-06 18:15 ` Steven Rostedt
2010-04-06 21:17 ` David Miller
2010-04-06 9:50 ` David Miller
2010-04-06 10:19 ` Frederic Weisbecker
2010-04-06 10:28 ` David Miller [this message]
2010-04-06 11:12 ` [RFC][PATCH] lockdep: WARN about local_irq_{en,dis}able in NMI context Peter Zijlstra
2010-04-06 11:13 ` David Miller
2010-04-06 11:20 ` Peter Zijlstra
2010-04-06 11:22 ` David Miller
2010-04-06 11:38 ` Random scheduler/unaligned accesses crashes with perf lock events on sparc 64 Frederic Weisbecker
2010-04-06 11:51 ` Peter Zijlstra
2010-04-06 12:54 ` Mike Galbraith
2010-04-06 12:57 ` Peter Zijlstra
2010-04-06 18:04 ` Paul E. McKenney
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=20100406.032850.137831355.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=rostedt@goodmis.org \
--cc=sparclinux@vger.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
Powered by JetHome