All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <david.daney@cavium.com>
Cc: linux-mips@linux-mips.org, James Hogan <james.hogan@imgtec.com>,
	linux-kernel@vger.kernel.org,
	Alex Belits <alex.belits@cavium.com>
Subject: Re: [PATCH] MIPS: Add 48-bit VA space (and 4-level page tables) for 4K pages.
Date: Wed, 15 Mar 2017 14:34:46 +0100	[thread overview]
Message-ID: <20170315133446.GD5512@linux-mips.org> (raw)
In-Reply-To: <20170217012734.19256-1-david.daney@cavium.com>

On Thu, Feb 16, 2017 at 05:27:34PM -0800, David Daney wrote:

> From: Alex Belits <alex.belits@cavium.com>
> 
> Some users must have 4K pages while needing a 48-bit VA space size.
> The cleanest way do do this is to go to a 4-level page table for this
> case.  Each page table level using order-0 pages adds 9 bits to the
> VA size (at 4K pages, so for four levels we get 9 * 4 + 12 == 48-bits.
> 
> For the 4K page size case only we add support functions for the PUD
> level of the page table tree, also the TLB exception handlers get an
> extra level of tree walk.
> 
> Signed-off-by: Alex Belits <alex.belits@cavium.com>
> [david.daney@cavium.com] Forward port to v4.10
> Signed-off-by: David Daney <david.daney@cavium.com>

Thanks folks, queued for 4.12.

While the need for 48-bit address space is not so surprising, the need
for the combination of 4K pages and 48-bit address space is!

I had some minor merge conflicts so it would be good if you could take
a look if https://git.linux-mips.org/cgit/ralf/upstream-sfr.git/commit/?id=afba1896993a0b74aa2ad3076d594e455b3af301
looks good.

  Ralf

      reply	other threads:[~2017-03-15 15:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17  1:27 [PATCH] MIPS: Add 48-bit VA space (and 4-level page tables) for 4K pages David Daney
2017-03-15 13:34 ` Ralf Baechle [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=20170315133446.GD5512@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=alex.belits@cavium.com \
    --cc=david.daney@cavium.com \
    --cc=james.hogan@imgtec.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@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 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.