From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Todd Inglett <tinglett@us.ibm.com>,
linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
Volkmar Uhlig <vuhlig@us.ibm.com>, David Gibson <dwg@au1.ibm.com>
Subject: Re: Fix small race in 44x tlbie function
Date: Thu, 09 Aug 2007 17:01:31 +1000 [thread overview]
Message-ID: <1186642891.938.219.camel@localhost.localdomain> (raw)
In-Reply-To: <CEBBAD6A-9C83-4E9A-9752-8F089894E56C@kernel.crashing.org>
On Thu, 2007-08-09 at 01:35 -0500, Kumar Gala wrote:
> >>>> Did you actually see this happen?
> >>>
> >>> Yes.
> >>
> >> When?
> >>
> >> We don't have critical wired to anything, I don't expect watchdog to
> >> cause another fault.. so just wondering.
> >
> > On debug (trace) interrupts on blue gene.
>
> Do you know why the debug code caused a fault?
Sure, it may access vmalloc space for example, which can cause a TLB
miss...
Ben.
next prev parent reply other threads:[~2007-08-09 7:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 4:20 Fix small race in 44x tlbie function David Gibson
2007-08-08 14:49 ` Josh Boyer
2007-08-08 15:20 ` Kumar Gala
2007-08-08 16:00 ` Josh Boyer
2007-08-09 5:28 ` Kumar Gala
2007-08-09 5:34 ` David Gibson
2007-08-09 6:35 ` Kumar Gala
2007-08-09 7:01 ` Benjamin Herrenschmidt [this message]
2007-08-09 12:04 ` Josh Boyer
2007-08-09 13:05 ` Benjamin Herrenschmidt
2007-08-09 13:26 ` Josh Boyer
2007-08-08 20:43 ` Hollis Blanchard
2007-08-08 21:29 ` Josh Boyer
2007-08-08 22:11 ` Hollis Blanchard
2007-08-08 23:30 ` Benjamin Herrenschmidt
2007-08-08 23:41 ` Josh Boyer
2007-08-08 23:01 ` Benjamin Herrenschmidt
2007-08-09 0:06 ` Josh Boyer
-- strict thread matches above, loose matches on Subject: below --
2007-08-08 15:34 Volkmar Uhlig
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=1186642891.938.219.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=dwg@au1.ibm.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=tinglett@us.ibm.com \
--cc=vuhlig@us.ibm.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.