linux-kernel - Re: [PATCH] ARM: Kconfig: improve ARM_SINGLE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <170aea55-44f3-9cf0-fd88-adf8c66efeb4@benettiengineering.com>
Date:   Fri, 3 Dec 2021 17:41:28 +0100
From:   Giulio Benetti <giulio.benetti@...ettiengineering.com>
To:     Vladimir Murzin <vladimir.murzin@....com>,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Cc:     Russell King <linux@...linux.org.uk>,
        Arnd Bergmann <arnd@...db.de>,
        Linus Walleij <linus.walleij@...aro.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        "Russell King (Oracle)" <rmk+kernel@...linux.org.uk>,
        Ard Biesheuvel <ardb@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        Anshuman Khandual <anshuman.khandual@....com>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        Mike Rapoport <rppt@...nel.org>,
        Uwe Kleine-König <u.kleine-koenig@...gutronix.de>,
        Lukas Bulwahn <lukas.bulwahn@...il.com>
Subject: Re: [PATCH] ARM: Kconfig: improve ARM_SINGLE_ARMV7M description with
 Cortex M7

Hi Vladimir,

On 03/12/21 10:30, Vladimir Murzin wrote:
> On 12/2/21 10:20 PM, Giulio Benetti wrote:
>> ARM_SINGLE_ARMV7M implies Arm Cortex M7 too, so let's add it to
>> description with M0/M3/M4.
> 
> Well it also implies M33 and M55. I'd suggest drop specific implementations
> from description - so we do not need to update it each time new compatible
> core is released. To account newest cores like M33 and M55 you can rephrase
> to:
> - ARMv7-M/v8-M

This ^^^ is ok for me. Also, I don't see any M0 used at the moment so no 
ARMv6-M makes sense, if any in the future we can update. I see M3,M4,M7 
for the moment, so ARMv7-M. But at the moment no ARMv8-M, or am I wrong?
Maybe it would be better to add ARMv8-M when there will really be the 
support, considering also that ARM_SINGLE_ARMV7M is a bit ambiguous to 
be used with ARMv8-M. So maybe that could be modified too when an 
ARMv8-M is added.

What do you think about this?

Best regards
-- 
Giulio Benetti
Benetti Engineering sas

> - ARMv7-M and above
> 
> Cheers
> Vladimir
> 
>>
>> Signed-off-by: Giulio Benetti <giulio.benetti@...ettiengineering.com>
>> ---
>>   arch/arm/Kconfig | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
>> index c2724d986fa0..67efbde70e34 100644
>> --- a/arch/arm/Kconfig
>> +++ b/arch/arm/Kconfig
>> @@ -329,7 +329,7 @@ config ARCH_MULTIPLATFORM
>>   	select USE_OF
>>   
>>   config ARM_SINGLE_ARMV7M
>> -	bool "ARMv7-M based platforms (Cortex-M0/M3/M4)"
>> +	bool "ARMv7-M based platforms (Cortex-M0/M3/M4/M7)"
>>   	depends on !MMU
>>   	select ARM_NVIC
>>   	select AUTO_ZRELADDR
>>
>