From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/11] Patches for Toshiba Cell reference set
Date: Wed, 07 Feb 2007 10:33:00 +1100 [thread overview]
Message-ID: <1170804780.2620.260.camel@localhost.localdomain> (raw)
In-Reply-To: <1170804615.2620.257.camel@localhost.localdomain>
On Wed, 2007-02-07 at 10:30 +1100, Benjamin Herrenschmidt wrote:
> On Wed, 2007-02-07 at 08:05 +1100, Paul Mackerras wrote:
> > Ishizaki Kou writes:
> >
> > > We found that following phenomenon:
> > > - An application calls "munmap"
> > > - do_munmap flushes TLB (so HTAB is invalidated)
> > > - when exiting spin_unlock(), DEC exception occurs. (!)
> > > - One of DEC handler causes data storage interrupt
> >
> > Interesting. Did you find out exactly what was causing the DSI in the
> > decrementer interrupt handling? It sounds like that is the real bug.
>
> Not necessarily... DEC -> module -> vmalloc'ed or ioremap'ed access for
> example would trigger a DSI.
>
> The Hash routines expect irqs off when called.
Argh ! Actually no ! They expect irqs off in insert and updatepp, not in
invalidate. You'll notice that iSeries invalidate does a
local_irq_disable.
Ishiazaki-san: The proper fix is to do that too for Celleb. That is,
continue using a normal spinlock and add a local_irq_save/restore in
your invalidate callback (and only that one).
I wonder if we should "clean" that up and move that to the caller
though, and thus have a more consisent interface to the hash code.
Ben.
next prev parent reply other threads:[~2007-02-06 23:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-02 7:34 [PATCH 0/11] Patches for Toshiba Cell reference set Ishizaki Kou
2007-02-04 23:55 ` Benjamin Herrenschmidt
2007-02-06 13:01 ` Ishizaki Kou
2007-02-06 21:05 ` Paul Mackerras
2007-02-06 23:30 ` Benjamin Herrenschmidt
2007-02-06 23:33 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-26 11:37 Ishizaki Kou
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=1170804780.2620.260.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).