linux-kernel - Re: [Intel-gfx] [PATCH v5 0/7] Introduce _

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 for Android: free password hash cracker in your pocket

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

Message-ID: <87r0fjc1cz.fsf@intel.com>
Date: Fri, 05 Apr 2024 17:47:56 +0300
From: Jani Nikula <jani.nikula@...ux.intel.com>
To: Peter Zijlstra <peterz@...radead.org>, Andrzej Hajda
 <andrzej.hajda@...el.com>
Cc: Mark Rutland <mark.rutland@....com>, linux-ia64@...r.kernel.org,
 linux-sh@...r.kernel.org, dri-devel@...ts.freedesktop.org,
 linux-kernel@...r.kernel.org, sparclinux@...r.kernel.org,
 linux-riscv@...ts.infradead.org, linux-s390@...r.kernel.org,
 linux-hexagon@...r.kernel.org, linux-snps-arc@...ts.infradead.org,
 intel-gfx@...ts.freedesktop.org, linux-xtensa@...ux-xtensa.org, Arnd
 Bergmann <arnd@...db.de>, Boqun Feng <boqun.feng@...il.com>,
 linux-m68k@...ts.linux-m68k.org, openrisc@...ts.librecores.org,
 loongarch@...ts.linux.dev, Rodrigo Vivi <rodrigo.vivi@...el.com>, Andy
 Shevchenko <andriy.shevchenko@...ux.intel.com>,
 linux-arm-kernel@...ts.infradead.org, linux-parisc@...r.kernel.org,
 linux-mips@...r.kernel.org, linux-alpha@...r.kernel.org, Andrew Morton
 <akpm@...ux-foundation.org>, linuxppc-dev@...ts.ozlabs.org
Subject: Re: [Intel-gfx] [PATCH v5 0/7] Introduce __xchg, non-atomic xchg

On Mon, 27 Feb 2023, Peter Zijlstra <peterz@...radead.org> wrote:
> On Thu, Feb 23, 2023 at 10:24:19PM +0100, Andrzej Hajda wrote:
>> On 22.02.2023 18:04, Peter Zijlstra wrote:
>> > On Wed, Jan 18, 2023 at 04:35:22PM +0100, Andrzej Hajda wrote:
>> > 
>> > > Andrzej Hajda (7):
>> > >    arch: rename all internal names __xchg to __arch_xchg
>> > >    linux/include: add non-atomic version of xchg
>> > >    arch/*/uprobes: simplify arch_uretprobe_hijack_return_addr
>> > >    llist: simplify __llist_del_all
>> > >    io_uring: use __xchg if possible
>> > >    qed: use __xchg if possible
>> > >    drm/i915/gt: use __xchg instead of internal helper
>> > 
>> > Nothing crazy in here I suppose, I somewhat wonder why you went through
>> > the trouble, but meh.
>> 
>> If you are asking why I have proposed this patchset, then the answer is
>> simple, 1st I've tried to find a way to move internal i915 helper to core
>> (see patch 7).
>> Then I was looking for possible other users of this helper. And apparently
>> there are many of them, patches 3-7 shows some.
>> 
>> 
>> > 
>> > You want me to take this through te locking tree (for the next cycle,
>> > not this one) where I normally take atomic things or does someone else
>> > want this?
>> 
>> If you could take it I will be happy.
>
> OK, I'll go queue it in tip/locking/core after -rc1. Thanks!

Is this where the series fell between the cracks, or was there some
follow-up that I missed?

I think this would still be useful. Andrzej, would you mind rebasing and
resending if there are no objections?

BR,
Jani.


-- 
Jani Nikula, Intel