From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Tim Deegan <tim@xen.org>, Ian Campbell <Ian.Campbell@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH] xen/x86: Map Xen code/data/bss with superpages
Date: Thu, 18 Feb 2016 18:20:55 +0000 [thread overview]
Message-ID: <56C60B87.7050502@citrix.com> (raw)
In-Reply-To: <1455818622-30625-1-git-send-email-andrew.cooper3@citrix.com>
On 18/02/16 18:03, Andrew Cooper wrote:
> And make use of NX and RO attributes wherever possible.
>
> Andrew Cooper (4):
> xen: Introduce IS_ALIGNED()
> xen/memguard: Drop memguard_init() entirely
> xen/x86: Use 2M superpages for text/data/bss mappings
> xen/x86: Unilaterally remove .init mappings
Apologies - I messed up with git format-patch and omitted the patch
numbers. (at least there are only 4)
The patches are available on
http://xenbits.xen.org/git-http/people/andrewcoop/xen.git xen-super-v1
~Andrew
prev parent reply other threads:[~2016-02-18 18:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 18:03 [PATCH] xen/x86: Map Xen code/data/bss with superpages Andrew Cooper
2016-02-18 18:03 ` [PATCH] xen: Introduce IS_ALIGNED() Andrew Cooper
2016-02-18 18:03 ` [PATCH] xen/memguard: Drop memguard_init() entirely Andrew Cooper
2016-02-19 14:44 ` Jan Beulich
2016-02-19 16:18 ` Andrew Cooper
2016-02-22 10:02 ` Jan Beulich
2016-02-22 10:29 ` Andrew Cooper
2016-02-22 10:41 ` Jan Beulich
2016-02-18 18:03 ` [PATCH] xen/x86: Use 2M superpages for text/data/bss mappings Andrew Cooper
2016-02-19 14:58 ` Jan Beulich
2016-02-19 15:51 ` Andrew Cooper
2016-02-22 9:55 ` Jan Beulich
2016-02-22 10:24 ` Andrew Cooper
2016-02-22 10:43 ` Jan Beulich
2016-02-18 18:03 ` [PATCH] xen/x86: Unilaterally remove .init mappings Andrew Cooper
2016-02-19 15:02 ` Jan Beulich
2016-02-18 18:20 ` Andrew Cooper [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=56C60B87.7050502@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=tim@xen.org \
--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 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.