From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Satya <satyakiran@gmail.com>
Cc: kazutomo@mcs.anl.gov, linuxppc-dev@ozlabs.org,
edi@linux.vnet.ibm.com, david@gibson.dropbear.id.au
Subject: Re: hugetlbfs for ppc440 - kernel BUG -- follow up
Date: Wed, 18 Jul 2007 13:01:26 +1000 [thread overview]
Message-ID: <1184727686.25235.203.camel@localhost.localdomain> (raw)
In-Reply-To: <acbcf3840707171918h5dee75d9t96d6a62e8a0161fa@mail.gmail.com>
On Tue, 2007-07-17 at 21:18 -0500, Satya wrote:
> the calling sequence is :
>
> __handle_mm_fault -> hugetlb_fault -> huge_pte_alloc() ->
> pte_alloc_map()
>
> where -> stands for 'calls'.
>
> hugetlb_fault() calls hugetlb_no_page() after returning from
> huge_pte_alloc().
>
> [huge_pte_alloc() is an arch specific call back implemented in the
> patch referred to in my earlier posts]
Ok, so I think the problem might be there. If you look at other
implementations of hugetlbfs, such as x86, there is no need to do any
mapping in huge_pte_alloc(). Only the PTE pages can be mapped/unmapped
and the huge pages are stored at the PMD level. You may want to do
something similar, and if you need a PTE level for huge pages
specifically, then you could do your own allocations there that don't
require a mapping.
Ben.
prev parent reply other threads:[~2007-07-18 3:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 21:07 hugetlbfs for ppc440 - kernel BUG -- follow up Satya
2007-07-18 1:53 ` Benjamin Herrenschmidt
2007-07-18 2:18 ` Satya
2007-07-18 3:01 ` 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=1184727686.25235.203.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=edi@linux.vnet.ibm.com \
--cc=kazutomo@mcs.anl.gov \
--cc=linuxppc-dev@ozlabs.org \
--cc=satyakiran@gmail.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).