From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Sachin Sant <sachinp@in.ibm.com>
Cc: Mel Gorman <mel@csn.ul.ie>, linuxppc-dev@ozlabs.org
Subject: Re: [OOPS] hugetlbfs tests with 2.6.30-rc8-git1
Date: Tue, 16 Jun 2009 11:30:28 +1000 [thread overview]
Message-ID: <1245115828.12400.48.camel@pasglop> (raw)
In-Reply-To: <4A3645EE.5060103@in.ibm.com>
On Mon, 2009-06-15 at 18:30 +0530, Sachin Sant wrote:
> 278: 2f 80 00 00 cmpwi cr7,r0,0
> } else {
> vsid = get_kernel_vsid(addr, mmu_kernel_ssize);
> ssize = mmu_kernel_ssize;
> }
> vaddr = hpt_va(addr, vsid, ssize);
> rpte = __real_pte(__pte(pte), ptep);
> 27c: eb 89 80 00 ld r28,-32768(r9)
I think I know what the problem is. I'll send a tentative patch as soon
as I got to test it a bit here.
Cheers,
Ben.
prev parent reply other threads:[~2009-06-16 1:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 11:29 [OOPS] hugetlbfs tests with 2.6.30-rc8-git1 Sachin Sant
2009-06-05 15:04 ` Mel Gorman
2009-06-05 15:48 ` Sachin Sant
2009-06-05 20:17 ` Benjamin Herrenschmidt
2009-06-06 19:51 ` Sachin Sant
2009-06-14 11:38 ` Sachin Sant
2009-06-15 0:56 ` Michael Ellerman
2009-06-15 1:38 ` Stephen Rothwell
2009-06-15 13:00 ` Sachin Sant
2009-06-15 21:26 ` Benjamin Herrenschmidt
2009-06-16 1:30 ` Benjamin Herrenschmidt [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=1245115828.12400.48.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mel@csn.ul.ie \
--cc=sachinp@in.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 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).