Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Sasha Levin <Alexander.Levin@microsoft.com>
To:     Vladimir Murzin <vladimir.murzin@arm.com>
CC:     "stable@vger.kernel.org" <stable@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Russell King <rmk+kernel@armlinux.org.uk>
Subject: Re: [PATCH AUTOSEL 4.14 49/89] ARM: 8783/1: NOMMU: Extend check for
 VBAR support
Thread-Topic: [PATCH AUTOSEL 4.14 49/89] ARM: 8783/1: NOMMU: Extend check for
 VBAR support
Thread-Index: AQHUQr3c+8f45WjXpUKg+K5Z8FLtkaTpT5WAgABLaYA=
Date:   Mon, 10 Sep 2018 14:12:00 +0000
Message-ID: <20180910141159.GP16300@sasha-vm>
References: <20180902064918.183387-1-alexander.levin@microsoft.com>
 <20180902064918.183387-49-alexander.levin@microsoft.com>
 <0cee99b8-fd6d-43b5-e553-2df2939bf40e@arm.com>
In-Reply-To: <0cee99b8-fd6d-43b5-e553-2df2939bf40e@arm.com>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: microsoft.com does not designate
 permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6BC5B038F9733C47A82B29E3F2DCD51C@namprd21.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: ea1941e4-7f23-49cb-1c27-08d61727607c
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Sep 2018 14:12:00.9003
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR21MB0779
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, Sep 10, 2018 at 10:42:05AM +0100, Vladimir Murzin wrote:
>On 02/09/18 14:07, Sasha Levin wrote:
>> From: Vladimir Murzin <vladimir.murzin@arm.com>
>>
>> [ Upstream commit c803ce3f18bd93b3b4a15d1da0c5b5ebc60e0b85 ]
>>
>> ARMv8R adds support for VBAR and updates ID_PFR1 with the new filed
>> Sec_frac (bits [23:20]):
>>
>> Security fractional field. When the Security field is 0000, determines
>> the support for features from the ARMv7 Security Extensions. Permitted
>> values are:
>>
>> 0000 No features from the ARMv7 Security Extensions are implemented.
>>      This value is not supported in ARMv8 if ID_PFR1 bits [7:4] are zero=
.
>>
>> 0001 The implementation includes the VBAR, and the TCR.PD0 and TCR.PD1
>>      bits.
>>
>> 0010 As for 0001, plus the ability to access Secure or Non-secure
>>      physical memory is supported.
>>
>> All other values are reserved.
>>
>> This field is only valid when ID_PFR1[7:4] =3D=3D 0, otherwise it holds
>> the value 0000.
>>
>> Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com>
>> Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
>> Signed-off-by: Sasha Levin <alexander.levin@microsoft.com>
>> ---
>>  arch/arm/mm/nommu.c | 3 ++-
>>  1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/arm/mm/nommu.c b/arch/arm/mm/nommu.c
>> index 91537d90f5f5..08794bb0cada 100644
>> --- a/arch/arm/mm/nommu.c
>> +++ b/arch/arm/mm/nommu.c
>> @@ -305,7 +305,8 @@ static inline bool security_extensions_enabled(void)
>>  {
>>  	/* Check CPUID Identification Scheme before ID_PFR1 read */
>>  	if ((read_cpuid_id() & 0x000f0000) =3D=3D 0x000f0000)
>> -		return !!cpuid_feature_extract(CPUID_EXT_PFR1, 4);
>> +		return cpuid_feature_extract(CPUID_EXT_PFR1, 4) ||
>> +			cpuid_feature_extract(CPUID_EXT_PFR1, 20);
>>  	return 0;
>>  }
>>
>>
>
>NAK - it is not stable material.

Dropped from all trees. Thank you.=