From: linas@austin.ibm.com (Linas Vepstas)
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
benh@samba.org
Subject: Re: Page faults blowing up ... [was Re: [PATCH] Fix special PTE code for secondary hash bucket
Date: Mon, 6 Aug 2007 14:19:00 -0500 [thread overview]
Message-ID: <20070806191900.GC4357@austin.ibm.com> (raw)
In-Reply-To: <1186194688.5733.6.camel@gruick>
On Sat, Aug 04, 2007 at 12:31:28PM +1000, Benjamin Herrenschmidt wrote:
>
> Paulus stuff is likely to be unrelated to your bug. Also, whatever blurb
> you pasted in this email is totally incomprehensible due to total lack
> of context.
Sorry. Mike Strosaker nailed it; its a nutty hypervisor bug.
--linas
prev parent reply other threads:[~2007-08-06 19:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 8:58 [PATCH] Fix special PTE code for secondary hash bucket Paul Mackerras
2007-08-03 11:51 ` Benjamin Herrenschmidt
2007-08-03 19:32 ` Page faults blowing up ... [was " Linas Vepstas
2007-08-03 21:54 ` Mike Strosaker
2007-08-04 2:31 ` Benjamin Herrenschmidt
2007-08-06 19:19 ` Linas Vepstas [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=20070806191900.GC4357@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=benh@samba.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).