linux-kernel - Re: [PATCH 1/2] MIPS: Allow MIPS32R2 kernel to run on P5600 and M5150

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]

Date:   Tue, 30 May 2023 09:03:32 +0100 (BST)
From:   "Maciej W. Rozycki" <macro@...am.me.uk>
To:     Jiaxun Yang <jiaxun.yang@...goat.com>,
        Paul Cercueil <paul@...pouillou.net>
cc:     linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org,
        Thomas Bogendoerfer <tsbogend@...ha.franken.de>
Subject: Re: [PATCH 1/2] MIPS: Allow MIPS32R2 kernel to run on P5600 and
 M5150

On Mon, 29 May 2023, Jiaxun Yang wrote:

> M5150 and P5600 are two MIPS32R5 kernels, however as MIPS32R5 is
> backward compatible with MIPS32R2 there is no reason to forbid
> M5150 and P5600 on MIPS32R2 kernel.

 What problem are you trying to solve?  The CONFIG_SYS_HAS_CPU_* settings 
denote overall platform's support for the given CPU and have nothing to do 
with what architecture level a given kernel has been configured for.  You 
do need to get the settings right for your platform, just as you do in 
2/2, but this 1/2 part looks wrong to me.

 NB CPU_4KEC is double-listed as R1 and R2 because early revisions of the 
4KEc core were actually R1 before switching to R2, so this CPU can report 
either revision.

 I don't know why CPU_XBURST is also listed as both R1 and R2, the history 
looks convoluted with no explanation.  Paul, is the CPU also dual-revision 
or is it just a bug and it is supposed to be listed under one ISA revision
only, presumably R2?

  Maciej