linux-kernel - Re: [PATCH 08/13] locking/qspinlock: stop renaming queued_spin_lock_slowpath to native_queued_spin_lock

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, 5 Jul 2022 19:28:43 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Nicholas Piggin <npiggin@...il.com>
Cc:     Ingo Molnar <mingo@...hat.com>, Will Deacon <will@...nel.org>,
        Waiman Long <longman@...hat.com>,
        Boqun Feng <boqun.feng@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 08/13] locking/qspinlock: stop renaming
 queued_spin_lock_slowpath to native_queued_spin_lock_slowpath

On Tue, Jul 05, 2022 at 12:38:15AM +1000, Nicholas Piggin wrote:
> The native version can simply be queued_spin_lock_slowpath, and the
> paravirt version __pv_queued_spin_lock_slowpath, which is as they are
> named in the C code.
> 

Humm... so it is the x86 paravirt convention to have native_*()
functions for everthing, which sometimes are unconditionally called
whenever the paravirt indirection is unwarranted etc..

I suppose that's not the case with the spinlock code thouhg, so yeah,
why not.