From: David Daney <ddaney.cavm@gmail.com>
To: "Steven J. Hill" <Steven.Hill@imgtec.com>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: Re: [PATCH V7 1/3] MIPS: Rearrange PTE bits into fixed positions.
Date: Thu, 26 Feb 2015 16:51:41 -0800 [thread overview]
Message-ID: <54EFBF9D.4020004@gmail.com> (raw)
In-Reply-To: <1424996199-21366-2-git-send-email-Steven.Hill@imgtec.com>
On 02/26/2015 04:16 PM, Steven J. Hill wrote:
> From: "Steven J. Hill" <Steven.Hill@imgtec.com>
>
> This patch rearranges the PTE bits into fixed positions for R2
> and later cores. In the past, the TLB handling code did runtime
> checking of RI/XI and adjusted the shifts and rotates in order
> to fit the largest PFN value into the PTE. The checking now
> occurs when building the TLB handler, thus eliminating those
> checks. These new arrangements also define the largest possible
> PFN value that can fit in the PTE. HUGE page support is only
> available for 64-bit cores. Layouts of the PTE bits are now:
>
> 64-bit, R1 or earlier: CCC D V G [S H] M A W R P
> 32-bit, R1 or earler: CCC D V G M A W R P
> 64-bit, R2 or later: CCC D V G RI/R XI [S H] M A W P
> 32-bit, R2 or later: CCC D V G RI/R XI M A W P
>
That's not really what I meant in my previous response on the subject.
When I said:
Why not just use RI for everything, instead of taking up two bits
to represent a single binary concept?
For the case where there is no RI hardware active, it is a purely
software bit and you can easily invert the meaning and just have a
_PAGE_NO_READ bit.
I envisioned something like:
64-bit, all revisions: CCC D V G RI XI [S H] M A W P
32-bit, all revisions: CCC D V G RI XI M A W P
Are there enough bits to include XI even if hardware doens't support XI?
David Daney
next prev parent reply other threads:[~2015-02-27 0:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 0:16 [PATCH V7 0/3] Add support for eXtended Physical Addressing Steven J. Hill
2015-02-27 0:16 ` [PATCH V7 1/3] MIPS: Rearrange PTE bits into fixed positions Steven J. Hill
2015-02-27 0:51 ` David Daney [this message]
2015-02-27 3:38 ` Steven J. Hill
2015-02-27 3:38 ` Steven J. Hill
2015-02-27 17:52 ` David Daney
2015-02-27 19:04 ` Steven J. Hill
2015-02-27 19:04 ` Steven J. Hill
2015-02-27 19:20 ` David Daney
2015-07-09 4:23 ` Huacai Chen
2015-02-27 0:16 ` [PATCH V7 2/3] MIPS: Add support for XPA Steven J. Hill
2015-02-27 0:16 ` [PATCH V7 3/3] MIPS: XPA: Add new configuration file Steven J. Hill
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=54EFBF9D.4020004@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=Steven.Hill@imgtec.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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