From: lauraa@codeaurora.org (Laura Abbott)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv7 2/2] arm64: add better page protections to arm64
Date: Tue, 20 Jan 2015 11:38:22 -0800 [thread overview]
Message-ID: <54BEAEAE.8010700@codeaurora.org> (raw)
In-Reply-To: <20150120184054.GJ25575@e104818-lin.cambridge.arm.com>
On 1/20/2015 10:40 AM, Catalin Marinas wrote:
> On Tue, Jan 20, 2015 at 06:19:23PM +0000, Kees Cook wrote:
>> If, however, only the name is stopping it from landing in arm64, then
>> I don't care what it's called. ;)
>
> Apart from couple of comments on this latest series, the patches look
> fine to me.
>
Did that message get sent out? I don't see it in my inbox.
> One question for Laura though: have the patches been tested it with:
>
> - 4-levels and 4KB pages?
> - 3-levels and 64KB pages?
>
Yes, just re-verified once again that both 4 level 4K pages and 3 level
64K pages work with this series.
Thanks,
Laura
--
Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-01-20 19:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 22:59 [PATCHv7 0/2] Better page protections for arm64 Laura Abbott
2015-01-14 22:59 ` [PATCHv7 1/2] arm64: use fixmap for text patching Laura Abbott
2015-01-15 11:21 ` Mark Rutland
2015-01-14 22:59 ` [PATCHv7 2/2] arm64: add better page protections to arm64 Laura Abbott
2015-01-15 9:44 ` Ard Biesheuvel
2015-01-15 16:36 ` Kees Cook
2015-01-17 0:26 ` Laura Abbott
2015-01-20 18:14 ` Catalin Marinas
2015-01-20 18:19 ` Kees Cook
2015-01-20 18:40 ` Catalin Marinas
2015-01-20 19:38 ` Laura Abbott [this message]
2015-01-21 15:44 ` Catalin Marinas
2015-01-20 19:46 ` Laura Abbott
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=54BEAEAE.8010700@codeaurora.org \
--to=lauraa@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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).