From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [RFC] [patch 4/6 -rt] powerpc 2.6.20-rt8: fix a runtime warnings for xmon
Date: Wed, 07 Mar 2007 11:10:59 +0100 [thread overview]
Message-ID: <1173262259.9349.40.camel@localhost.localdomain> (raw)
In-Reply-To: <20070307091638.GC1783@elte.hu>
On Wed, 2007-03-07 at 10:16 +0100, Ingo Molnar wrote:
> * Tsutomu OWA <tsutomu.owa@toshiba.co.jp> wrote:
>
> > @@ -342,6 +342,7 @@ static int xmon_core(struct pt_regs *reg
> >
> > msr = mfmsr();
> > mtmsr(msr & ~MSR_EE); /* disable interrupts */
> > + preempt_disable();
>
> i'm not an xmon expert, but maybe it might make more sense to first
> disable preemption, then interrupts - otherwise you could be preempted
> right after having disabled these interrupts (and be scheduled to
> another CPU, etc.). What is the difference between local_irq_save() and
> the above 'disable interrupts' sequence? If it's not the same and
> xmon_core() relied on having hardirqs disabled then it might make sense
> to do a local_irq_save() there, instead of a preempt_disable().
powerpc 64 bits nowadays does lazy HW masking, so local_irq_disable()
will not actually switch MSR_EE off. However, xmon needs that to happen
(though we have a nicer accessor to do it, I suspect some bitrot need
fixing in there, possibly already fixed in .21)
I agree that preempt_disable() should be put before the MSR tweaking
though.
Ben.
next prev parent reply other threads:[~2007-03-07 10:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 1:34 [patch 0/6 -rt] powerpc 2.6.20-rt8: fix boot/runtime errors/warnings for PowerPC(ppc64) Tsutomu OWA
2007-03-07 1:36 ` [patch 1/6 -rt] powerpc 2.6.20-rt8: add preemption checks for NEED_RESCHED_DELAYED Tsutomu OWA
2007-03-16 19:20 ` Sergei Shtylyov
2007-03-19 0:00 ` Tsutomu OWA
2007-03-07 1:37 ` [patch 2/6 -rt] powerpc 2.6.20-rt8: to convert spinlocks to raw ones Tsutomu OWA
2007-03-07 14:38 ` Sergei Shtylyov
2007-03-07 14:43 ` Benjamin Herrenschmidt
2007-03-07 14:54 ` Sergei Shtylyov
2007-03-07 16:49 ` Paul Mackerras
2007-03-07 17:30 ` Sergei Shtylyov
2007-03-07 19:21 ` Paul Mackerras
2007-03-07 21:21 ` Sergei Shtylyov
2007-03-07 21:30 ` Paul Mackerras
2007-03-08 0:43 ` Bill Huey
2007-03-08 3:26 ` Paul Mackerras
2007-03-08 4:00 ` Bill Huey
2007-03-07 1:39 ` [patch 3/6 -rt] powerpc 2.6.20-rt8: fix a runtime warning for smp_processor_id() Tsutomu OWA
2007-03-07 1:42 ` [RFC] [patch 4/6 -rt] powerpc 2.6.20-rt8: fix a runtime warnings for xmon Tsutomu OWA
2007-03-07 9:16 ` Ingo Molnar
2007-03-07 10:10 ` Benjamin Herrenschmidt [this message]
2007-03-07 10:54 ` Tsutomu OWA
2007-03-07 11:06 ` Arnd Bergmann
2007-03-07 1:45 ` [RFC] [patch 5/6] powerpc 2.6.20-rt8: fix a boot error for handle_percpu_irq Tsutomu OWA
2007-03-07 21:29 ` Sergei Shtylyov
2007-03-07 1:47 ` [patch 6/6 -rt] powerpc 2.6.20-rt8: fix boot/runtime errors/warnings Tsutomu OWA
2007-03-07 9:13 ` [patch 0/6 -rt] powerpc 2.6.20-rt8: fix boot/runtime errors/warnings for PowerPC(ppc64) Ingo Molnar
2007-03-07 14:26 ` Sergei Shtylyov
2007-03-08 2:28 ` Tsutomu OWA
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=1173262259.9349.40.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
/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).