From: cov@codeaurora.org (Christopher Covington)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/1] arm64: Add support for 48-bit Physical Address
Date: Wed, 26 Feb 2014 08:49:50 -0500 [thread overview]
Message-ID: <530DF0FE.3050602@codeaurora.org> (raw)
In-Reply-To: <1393394310-6138-2-git-send-email-mohun106@gmail.com>
Hi Radha,
On 02/26/2014 12:58 AM, mohun106 at gmail.com wrote:
> From: Radha Mohan Chintakuntla <rchintakuntla@cavium.com>
>
> Added support for ARMv8 platforms that have 48-bit physical address
> implemented. There is no change in the VA bits and levels of
> translation.
Is there benefit to using build-time constants for this information? Why not
look up the physical address range at run time, so that a single kernel binary
could run on any system?
Thanks,
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
next prev parent reply other threads:[~2014-02-26 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 5:58 [RFC PATCH 0/1] arm64: 48-bit Physical Address support mohun106 at gmail.com
2014-02-26 5:58 ` [RFC PATCH 1/1] arm64: Add support for 48-bit Physical Address mohun106 at gmail.com
2014-02-26 13:49 ` Christopher Covington [this message]
2014-02-26 14:08 ` Catalin Marinas
2014-02-26 14:27 ` Radha Mohan
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=530DF0FE.3050602@codeaurora.org \
--to=cov@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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).