From: vladimir.murzin@arm.com (Vladimir Murzin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/4] ARM: nommu: dynamic exception base address setting
Date: Thu, 9 Mar 2017 12:55:52 +0000 [thread overview]
Message-ID: <49b9120d-bafa-e6ba-53c5-5bedd328d628@arm.com> (raw)
In-Reply-To: <20170309124640.GA8369@afzalpc>
On 09/03/17 12:46, afzal mohammed wrote:
> Hi,
>
> On Thu, Mar 09, 2017 at 09:51:58AM +1000, Greg Ungerer wrote:
>> The patch below works too. Thanks for the quick response.
>
> Thanks Greg for verifying
>
> Vladimir, would the diff like below okay ?
Well, we should ask Russell which version he (dis)likes :)
Cheers
Vladimir
>
> Regards
> afzal
>
>>> ---8<---
>>> diff --git a/arch/arm/mm/nommu.c b/arch/arm/mm/nommu.c
>>> index 3b5c7aaf9c76..081562f5436e 100644
>>> --- a/arch/arm/mm/nommu.c
>>> +++ b/arch/arm/mm/nommu.c
>>> @@ -303,7 +303,9 @@ static inline void set_vbar(unsigned long val)
>>> */
>>> static inline bool security_extensions_enabled(void)
>>> {
>>> - return !!cpuid_feature_extract(CPUID_EXT_PFR1, 4);
>>> + if ((read_cpuid_id() & 0x000F0000) == 0x000F0000)
>>> + return !!cpuid_feature_extract(CPUID_EXT_PFR1, 4);
>>> + return 0;
>>> }
>>>
>>> static unsigned long __init setup_vectors_base(void)
>>>
>
next prev parent reply other threads:[~2017-03-09 12:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <314159a7-b664-1256-647d-c05880ad7710@uclinux.org>
2017-03-08 9:56 ` [PATCH v2 2/4] ARM: nommu: dynamic exception base address setting Vladimir Murzin
2017-03-08 12:39 ` Greg Ungerer
2017-03-08 16:22 ` afzal mohammed
2017-03-08 23:51 ` Greg Ungerer
2017-03-09 12:46 ` afzal mohammed
2017-03-09 12:55 ` Vladimir Murzin [this message]
2017-03-10 14:08 ` afzal mohammed
2017-01-22 3:16 [PATCH v2 0/4] ARM: v7-A !MMU support, prepare CONFIG_VECTORS_BASE removal afzal mohammed
2017-01-22 3:20 ` [PATCH v2 2/4] ARM: nommu: dynamic exception base address setting afzal mohammed
2017-01-22 3:20 ` afzal mohammed
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=49b9120d-bafa-e6ba-53c5-5bedd328d628@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.