[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <35c12a89-6a9f-0e43-5b84-375ab428a8bc@gentwo.org>
Date: Tue, 6 Aug 2024 13:32:43 -0700 (PDT)
From: "Christoph Lameter (Ampere)" <cl@...two.org>
To: Uros Bizjak <ubizjak@...il.com>
cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Dennis Zhou <dennis@...nel.org>, Tejun Heo <tj@...nel.org>,
Andy Lutomirski <luto@...nel.org>, Ingo Molnar <mingo@...nel.org>,
Nadav Amit <nadav.amit@...il.com>, Brian Gerst <brgerst@...il.com>,
Denys Vlasenko <dvlasenk@...hat.com>, "H . Peter Anvin" <hpa@...or.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>, Borislav Petkov <bp@...en8.de>,
Luc Van Oostenryck <luc.vanoostenryck@...il.com>
Subject: Re: [RFC PATCH 0/3] Enable strict percpu address space checks
On Mon, 5 Aug 2024, Uros Bizjak wrote:
> Also, the last patch hijacks __percpu tag and repurposes it as a named
> address space qualifier. While this works surprisingly well in this RFC
> patchset, I would really appreciate some help on how to rewrite this
> hack into some "production ready" code.
This looks like good work to find issues with per cpu macro usage. Per cpu
macros are a bit esoteric and it would be a good benefit if you can
get this done.
Sadly I cannot help you much with the address space qualifier.
Powered by blists - more mailing lists