From: Scott Wood <scottwood@freescale.com>
To: telenn barz <telenn.barz@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Questions on Hugetlb for bookE and PHYS_64BIT
Date: Fri, 15 Jun 2012 13:11:56 -0500 [thread overview]
Message-ID: <4FDB7AEC.2010102@freescale.com> (raw)
In-Reply-To: <CAE2rjsQpZzMaJQrNQexy7kUSVR6F09Nsuxi6ueKiLAh=Hj-G4Q@mail.gmail.com>
On 06/15/2012 09:43 AM, telenn barz wrote:
> Hi all,
>
> CONFIG_PHYS_64BIT enables kernel support for larger than 32-bit physical
> addresses. Is it this configuration option we have to enable for the
> support of 36-bit real memory (as are capable the Freescale e500v2 or
> e500mc cores family) ?
Yes.
> The Hugetlb patch for BookE
> (https://lists.ozlabs.org/pipermail/linuxppc-dev/2011-June/091315.html)
> seems to be surbordinated to CONFIG_PHYS_64BIT. Is there any good reason
> why it is not supported when CONFIG_PHYS_64BIT is disabled ?
Because it would be extra work to support that configuration, and
nobody's felt enough of a need for it to put in that work.
-Scott
next prev parent reply other threads:[~2012-06-15 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 14:43 Questions on Hugetlb for bookE and PHYS_64BIT telenn barz
2012-06-15 18:11 ` Scott Wood [this message]
2012-06-18 14:22 ` Becky Bruce
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=4FDB7AEC.2010102@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=telenn.barz@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 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.