From: vladimir.murzin@arm.com (Vladimir Murzin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mm: Enable PXN when running non-LPAE kernel on LPAE
Date: Tue, 29 Dec 2015 13:48:52 +0000 [thread overview]
Message-ID: <56828F44.9030204@arm.com> (raw)
In-Reply-To: <1451341389.25978.39.camel@decadent.org.uk>
On 28/12/15 22:23, Ben Hutchings wrote:
> On Mon, 2015-12-28 at 19:31 +0900, Jungseung Lee wrote:
>> 2015-05-11 23:36 GMT+09:00 Catalin Marinas <catalin.marinas@arm.com>:
>>> On Mon, May 11, 2015 at 05:09:35PM +0900, Jungseung Lee wrote:
>>>> Hi, Ben.
>>>>
>>>> 2014-12-25 2:20 GMT+09:00 Catalin Marinas :
>>>>> On Wed, Dec 24, 2014 at 03:54:28PM +0000, Ben Hutchings wrote:
>>>>>> The VMSA field of MMFR0 (bottom 4 bits) is incremented for each
>>>>>> added feature. PXN is supported if the value is >= 4 and LPAE
>>>>>> is supported if it is >= 5.
>>>>>>
>>>>>> In case a kernel with CONFIG_ARM_LPAE disabled is used on a
>>>>>> processor that supports LPAE, we can still use PXN in short
>>>>>> descriptors. So check for >= 4 not == 4.
>>>>>>
>>>>>> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
>>>>>> Cc: Jungseung Lee <js07.lee@gmail.com>
>>>>>> Cc: Catalin Marinas <catalin.marinas@arm.com>
>>>>>
>>>>> Acked-by: Catalin Marinas <catalin.marinas@arm.com>
>>>>
>>>> Is this patch handled?
>>>
>>> If it's not in mainline already, than it probably isn't handled.
>>>
>>>> or you can send it to Russell's patch system:
>>>> http://www.arm.linux.org.uk/developer/patches/
>>>
>>> Check mainline first, otherwise please submit it.
>>>
>>
>>> --
>>> Catalin
>>
>> Hi, Ben
>>
>> It looks still not submitted yet. Could you send it to Russell's patch
>> system?
>> http://www.arm.linux.org.uk/developer/patches/
>>
>
> I've never needed to use a web-based system to submit kernel patches
> before, and I'm not going to start now. Someone else can re-submit
You don't have to... I just quote Catalin's recipe [1]
> You can send patches as usual to patches at arm.linux.org.uk, just add
> KernelVersion: v3.?? after the --- line in your patch (maybe this could
> be automate as well but I didn't bother).
>
> For series, because the arrival order is not guaranteed, I use the git
> alias below to trick it into sleeping 60s between patches:
>
> ksend-rmk-patch = !git send-email --annotate --no-thread --suppress-cc=all --to-cmd='sleep 60 && echo patches at arm.linux.org.uk "#"'
>
> For stgit, I have a dedicated template:
>
> From: %(sender)s
> To: patches at arm.linux.org.uk
> Subject: %(prefix)s%(shortdescr)s
>
> %(longdescr)s
> PATCH FOLLOWS
> KernelVersion:%(version)s
> %(diff)s
>
> And there is always git pull request that Russell is happy with.
Does it work for you?
[1] https://lkml.org/lkml/2014/8/22/228
Happy NY
Vladimir
> this if they want it.
>
> Ben.
>
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
next prev parent reply other threads:[~2015-12-29 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <005201d1415a$e5fe5ed0$b1fb1c70$@samsung.com>
2015-12-28 22:23 ` [PATCH] ARM: mm: Enable PXN when running non-LPAE kernel on LPAE Ben Hutchings
2015-12-29 13:48 ` Vladimir Murzin [this message]
2015-12-29 14:11 ` Ben Hutchings
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=56828F44.9030204@arm.com \
--to=vladimir.murzin@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 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.