From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM64: Kernel managed pages are only flushed
Date: Wed, 12 Mar 2014 14:56:53 +0000 [thread overview]
Message-ID: <20140312145653.GA9691@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <b9ecee11764146c98dd41b811ebc05ae@BN1PR03MB266.namprd03.prod.outlook.com>
On Wed, Mar 12, 2014 at 02:41:31PM +0000, Bharat.Bhushan at freescale.com wrote:
> Did you get the chance to look into this? What is your take for this patch
> or you want to suggest some other solution?
See my reply to Laura here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-March/238510.html
We *really* don't want executable device mappings.
Will
next prev parent reply other threads:[~2014-03-12 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 11:20 [PATCH] ARM64: Kernel managed pages are only flushed Bharat Bhushan
2014-03-06 6:53 ` Catalin Marinas
2014-03-06 9:33 ` Bharat.Bhushan at freescale.com
2014-03-12 14:41 ` Bharat.Bhushan at freescale.com
2014-03-12 14:56 ` Will Deacon [this message]
2014-03-12 16:03 ` Catalin Marinas
2014-03-12 17:26 ` Catalin Marinas
2014-03-12 20:12 ` Laura Abbott
2014-03-13 11:00 ` Bharat.Bhushan at freescale.com
2014-03-26 3:16 ` Bharat.Bhushan at freescale.com
2014-03-27 10:55 ` Catalin Marinas
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=20140312145653.GA9691@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--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).