linux-kernel - Re: [PATCH v3 11/12] RISC-V: Use Linux logical cpu number instead of hartid

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:   Mon, 10 Sep 2018 18:35:45 -0700
From:   Atish Patra <atish.patra@....com>
To:     Christoph Hellwig <hch@...radead.org>
Cc:     "palmer@...ive.com" <palmer@...ive.com>,
        "linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>,
        "anup@...infault.org" <anup@...infault.org>,
        "mark.rutland@....com" <mark.rutland@....com>,
        Damien Le Moal <Damien.LeMoal@....com>,
        "jason@...edaemon.net" <jason@...edaemon.net>,
        "ard.biesheuvel@...aro.org" <ard.biesheuvel@...aro.org>,
        "marc.zyngier@....com" <marc.zyngier@....com>,
        "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
        "dmitriy@...-tech.org" <dmitriy@...-tech.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "jeremy.linton@....com" <jeremy.linton@....com>,
        "catalin.marinas@....com" <catalin.marinas@....com>,
        "tglx@...utronix.de" <tglx@...utronix.de>
Subject: Re: [PATCH v3 11/12] RISC-V: Use Linux logical cpu number instead of
 hartid

On 9/10/18 4:29 AM, Christoph Hellwig wrote:
> On Thu, Sep 06, 2018 at 01:05:34AM -0700, Atish Patra wrote:
>> Setup the cpu_logical_map during boot. Moreover, every SBI call
>> and PLIC context are based on the physical hartid. Use the logical
>> cpu to hartid mapping to pass correct hartid to respective functions.
>>
>> Signed-off-by: Atish Patra <atish.patra@....com>
>> Reviewed-by  : Anup Patel <anup@...infault.org>
> 
> Same whitespace issue here.
> 
> Otherwise looks fine:
> 
> Reviewed-by: Christoph Hellwig <hch@....de>
> 

Fixed. Thanks for the review.

Regards,
Atish