From: Li Zhong <zhong@linux.vnet.ibm.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: Paul Mackerras <paulus@samba.org>,
PowerPC email list <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [RFC PATCH powerpc] try secondary hash before BUG in kernel_map_linear_page()
Date: Wed, 10 Apr 2013 13:29:19 +0800 [thread overview]
Message-ID: <1365571759.10616.11.camel@ThinkPad-T5421> (raw)
In-Reply-To: <20130410022107.GA15929@concordia>
On Wed, 2013-04-10 at 12:21 +1000, Michael Ellerman wrote:
> On Mon, Feb 25, 2013 at 05:29:35PM +0800, Li Zhong wrote:
> > This patch tries to fix following issue when CONFIG_DEBUG_PAGEALLOC
> > is enabled:
> >
> > [ 543.075675] ------------[ cut here ]------------
> > [ 543.075701] kernel BUG at arch/powerpc/mm/hash_utils_64.c:1239!
> > [ 543.075714] Oops: Exception in kernel mode, sig: 5 [#1]
Hi Michael,
Thanks for the review.
> So the issue is that kernel_map_linear_page() doesn't try the secondary
> hash slot.
It seems so.
> > The code is borrowed from that in __hash_page_huge().
>
> It is, and in fact there is another copy in hash_low_64.S - in assembler.
>
> So I think we should at least try and keep ourselves to two
> implementations, one in asm and one in C. So can you split it out into a
> helper routine called by both kernel_map_linear_page() and
> __hash_page_huge() ?
OK, I'll try to update it as you suggested.
Thanks, Zhong
> cheers
>
prev parent reply other threads:[~2013-04-10 5:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 9:29 [RFC PATCH powerpc] try secondary hash before BUG in kernel_map_linear_page() Li Zhong
2013-04-10 2:21 ` Michael Ellerman
2013-04-10 5:29 ` Li Zhong [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=1365571759.10616.11.camel@ThinkPad-T5421 \
--to=zhong@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael@ellerman.id.au \
--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).