xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>
Subject: [PATCH] Map Xen code/data/bss with superpages
Date: Wed, 24 Feb 2016 19:07:28 +0000	[thread overview]
Message-ID: <1456340856-3065-1-git-send-email-andrew.cooper3@citrix.com> (raw)

And make use of NX and RO attributes wherever possible.

After this series, the pagetable layout looks like:

(XEN) *** Dumping Xen text/data/bss mappings from ffff82d080000000
(XEN) l2_xenmap: ffff82d080814000, pa 00000000ac014000
(XEN)  L4[261] = 00000000ac017063 X S RW P
(XEN)   L3[322] = 00000000ac014063 X S RW P
(XEN)    L2[000] = 00000000ab8001e1 X Gl + S RO P   <- .text
(XEN)    L2[001] = 00000000aba001a1 X Gl + S RO P   <- .text
(XEN)    L2[002] = 80000000abc001a1 NX Gl + S RO P  <- .rodata
                                                    <- discarded .init
(XEN)    L2[004] = 80000000ac0001e3 NX Gl + S RW P  <- .data and .bss
(XEN)    L2[511] = 000000084da6f063 X S RW P        <- stubs

Andrew Cooper (8):
  xen/lockprof: Move .lockprofile.data into .rodata
  xen/x86: Improvements to build-time pagetable generation
  xen/x86: Construct the {l2,l3}_bootmap at compile time
  xen/memguard: Drop memguard_init() entirely
  xen/x86: Disable CR0.WP while applying alternatives
  xen/x86: Reorder .data and .init when linking
  xen/x86: Use 2M superpages for text/data/bss mappings
  xen/x86: Unilaterally remove .init mappings

 xen/arch/arm/xen.lds.S       |  15 ++++---
 xen/arch/x86/alternative.c   |   7 +++
 xen/arch/x86/boot/head.S     |  18 +++-----
 xen/arch/x86/boot/x86_64.S   |  44 +++++++++++++++---
 xen/arch/x86/mm.c            |  16 -------
 xen/arch/x86/setup.c         |  64 +++++++++++++++++++--------
 xen/arch/x86/x86_64/mm.c     |   4 --
 xen/arch/x86/xen.lds.S       | 103 ++++++++++++++++++++++++++++---------------
 xen/include/asm-arm/config.h |   1 +
 xen/include/asm-arm/mm.h     |   1 -
 xen/include/asm-x86/config.h |   1 +
 xen/include/asm-x86/mm.h     |   2 -
 xen/include/asm-x86/setup.h  |   5 +++
 xen/include/xen/spinlock.h   |   2 +-
 14 files changed, 178 insertions(+), 105 deletions(-)

-- 
2.1.4

             reply	other threads:[~2016-02-24 19:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24 19:07 Andrew Cooper [this message]
2016-02-24 19:07 ` [PATCH] xen/lockprof: Move .lockprofile.data into .rodata Andrew Cooper
2016-02-25 11:02   ` Stefano Stabellini
2016-02-25 11:12     ` Stefano Stabellini
2016-02-24 19:07 ` [PATCH] xen/x86: Improvements to build-time pagetable generation Andrew Cooper
2016-02-24 19:07 ` [PATCH] xen/x86: Construct the {l2, l3}_bootmap at compile time Andrew Cooper
2016-02-24 19:07 ` [PATCH] xen/memguard: Drop memguard_init() entirely Andrew Cooper
2016-02-24 19:07 ` [PATCH] xen/x86: Disable CR0.WP while applying alternatives Andrew Cooper
2016-02-24 19:07 ` [PATCH] xen/x86: Reorder .data and .init when linking Andrew Cooper
2016-02-24 19:07 ` [PATCH] xen/x86: Use 2M superpages for text/data/bss mappings Andrew Cooper
2016-02-24 19:07 ` [PATCH] xen/x86: Unilaterally remove .init mappings Andrew Cooper

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=1456340856-3065-1-git-send-email-andrew.cooper3@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=xen-devel@lists.xen.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).