linux-kernel - Re: [PATCH v3 10/12] RISC-V: Add logical CPU indexing for RISC-V

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: <20180910112759.GI12979@infradead.org>
Date:   Mon, 10 Sep 2018 04:27:59 -0700
From:   Christoph Hellwig <hch@...radead.org>
To:     Atish Patra <atish.patra@....com>
Cc:     palmer@...ive.com, linux-riscv@...ts.infradead.org,
        hch@...radead.org, anup@...infault.org, mark.rutland@....com,
        Damien.LeMoal@....com, jason@...edaemon.net,
        ard.biesheuvel@...aro.org, marc.zyngier@....com,
        gregkh@...uxfoundation.org, dmitriy@...-tech.org,
        linux-kernel@...r.kernel.org, jeremy.linton@....com,
        catalin.marinas@....com, tglx@...utronix.de
Subject: Re: [PATCH v3 10/12] RISC-V: Add logical CPU indexing for RISC-V

On Thu, Sep 06, 2018 at 01:05:33AM -0700, Atish Patra wrote:
> Currently, both linux cpu id and hardware cpu id are same.
> This is not recommended as it will lead to discontinuous cpu
> indexing in Linux. Moreover, kdump kernel will run from CPU0
> which would be absent if we follow existing scheme.
> 
> Implement a logical mapping between Linux cpu id and hardware
> cpuid to decouple these two. Always mark the boot processor as
> cpu0 and all other cpus get the logical cpu id based on their
> booting order.
> 
> Signed-off-by: Atish Patra <atish.patra@....com>
> Reviewed-by  : Anup Patel <anup@...infault.org>

drop the two spaces before the ":", please.

Otherwise looks good:

Reviewed-by: Christoph Hellwig <hch@....de>