From: Dave Hansen <dave.hansen@linux.intel.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, x86@kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: [RFC][PATCH 0/4] x86, mpx: Support larger address space (MAWA)
Date: Thu, 26 Jan 2017 14:40:05 -0800 [thread overview]
Message-ID: <20170126224005.A6BBEF2C@viggo.jf.intel.com> (raw)
Kirill is chugging right along getting his 5-level paging[1] patch set
ready to be merged. I figured I'd share an early draft of the MPX
support that will to go along with it.
Background: there is a lot more detail about what bounds tables are in
the changelog for fe3d197f843. But, basically MPX bounds tables help
us to store the ranges to which a pointer is allowed to point. The
tables are walked by hardware and they are indexed by the virtual
address of the pointer being checked.
A larger virtual address space (from 5-level paging) means that we
need larger tables. 5-level paging hardware includes a feature called
MPX Address-Width Adjust (MAWA) that grows the bounds tables so they
can address the new address space. MAWA is controlled independently
from the paging mode (via an MSR) so that old MPX binaries can run on
new hardware and kernels supporting 5-level paging.
But, since userspace is responsible for allocating the table that is
growing (the directory), we need to ensure that userspace and the
kernel agree about the size of these tables and the kernel can set the
MSR appropriately.
These are not quite ready to get applied anywhere, but I don't expect
the basics to change unless folks have big problems with this. The
only big remaining piece of work is to update the MPX selftest code.
Dave Hansen (4):
x86, mpx: introduce per-mm MPX table size tracking
x86, mpx: update MPX to grok larger bounds tables
x86, mpx: extend MPX prctl() to pass in size of bounds directory
x86, mpx: context-switch new MPX address size MSR
arch/x86/include/asm/mmu.h | 1 +
arch/x86/include/asm/mpx.h | 41 ++++++++++++++---
arch/x86/include/asm/msr-index.h | 1 +
arch/x86/include/asm/processor.h | 6 +--
arch/x86/mm/mpx.c | 79 ++++++++++++++++++++++++++++----
arch/x86/mm/pgtable.c | 2 +-
arch/x86/mm/tlb.c | 42 +++++++++++++++++
kernel/sys.c | 6 +--
8 files changed, 155 insertions(+), 23 deletions(-)
1. https://software.intel.com/sites/default/files/managed/2b/80/5-level_paging_white_paper.pdf
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <dave.hansen@linux.intel.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, x86@kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: [RFC][PATCH 0/4] x86, mpx: Support larger address space (MAWA)
Date: Thu, 26 Jan 2017 14:40:05 -0800 [thread overview]
Message-ID: <20170126224005.A6BBEF2C@viggo.jf.intel.com> (raw)
Kirill is chugging right along getting his 5-level paging[1] patch set
ready to be merged. I figured I'd share an early draft of the MPX
support that will to go along with it.
Background: there is a lot more detail about what bounds tables are in
the changelog for fe3d197f843. But, basically MPX bounds tables help
us to store the ranges to which a pointer is allowed to point. The
tables are walked by hardware and they are indexed by the virtual
address of the pointer being checked.
A larger virtual address space (from 5-level paging) means that we
need larger tables. 5-level paging hardware includes a feature called
MPX Address-Width Adjust (MAWA) that grows the bounds tables so they
can address the new address space. MAWA is controlled independently
from the paging mode (via an MSR) so that old MPX binaries can run on
new hardware and kernels supporting 5-level paging.
But, since userspace is responsible for allocating the table that is
growing (the directory), we need to ensure that userspace and the
kernel agree about the size of these tables and the kernel can set the
MSR appropriately.
These are not quite ready to get applied anywhere, but I don't expect
the basics to change unless folks have big problems with this. The
only big remaining piece of work is to update the MPX selftest code.
Dave Hansen (4):
x86, mpx: introduce per-mm MPX table size tracking
x86, mpx: update MPX to grok larger bounds tables
x86, mpx: extend MPX prctl() to pass in size of bounds directory
x86, mpx: context-switch new MPX address size MSR
arch/x86/include/asm/mmu.h | 1 +
arch/x86/include/asm/mpx.h | 41 ++++++++++++++---
arch/x86/include/asm/msr-index.h | 1 +
arch/x86/include/asm/processor.h | 6 +--
arch/x86/mm/mpx.c | 79 ++++++++++++++++++++++++++++----
arch/x86/mm/pgtable.c | 2 +-
arch/x86/mm/tlb.c | 42 +++++++++++++++++
kernel/sys.c | 6 +--
8 files changed, 155 insertions(+), 23 deletions(-)
1. https://software.intel.com/sites/default/files/managed/2b/80/5-level_paging_white_paper.pdf
next reply other threads:[~2017-01-26 22:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 22:40 Dave Hansen [this message]
2017-01-26 22:40 ` [RFC][PATCH 0/4] x86, mpx: Support larger address space (MAWA) Dave Hansen
2017-01-26 22:40 ` [RFC][PATCH 1/4] x86, mpx: introduce per-mm MPX table size tracking Dave Hansen
2017-01-26 22:40 ` Dave Hansen
2017-01-27 8:26 ` Ingo Molnar
2017-01-27 8:26 ` Ingo Molnar
2017-01-26 22:40 ` [RFC][PATCH 2/4] x86, mpx: update MPX to grok larger bounds tables Dave Hansen
2017-01-26 22:40 ` Dave Hansen
2017-01-26 22:40 ` [RFC][PATCH 3/4] x86, mpx: extend MPX prctl() to pass in size of bounds directory Dave Hansen
2017-01-26 22:40 ` Dave Hansen
2017-01-26 22:40 ` [RFC][PATCH 4/4] x86, mpx: context-switch new MPX address size MSR Dave Hansen
2017-01-26 22:40 ` Dave Hansen
2017-01-27 8:31 ` Ingo Molnar
2017-01-27 8:31 ` Ingo Molnar
2017-01-27 8:16 ` [RFC][PATCH 0/4] x86, mpx: Support larger address space (MAWA) Ingo Molnar
2017-01-27 8:16 ` Ingo Molnar
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=20170126224005.A6BBEF2C@viggo.jf.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=x86@kernel.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.