[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <C5B8B806-34CD-4654-992C-4FE3FAF85B88@vmware.com>
Date: Sat, 21 Oct 2023 14:39:30 +0000
From: Nadav Amit <namit@...are.com>
To: Uros Bizjak <ubizjak@...il.com>
CC: the arch/x86 maintainers <x86@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Andy Lutomirski <luto@...nel.org>,
Brian Gerst <brgerst@...il.com>,
Denys Vlasenko <dvlasenk@...hat.com>,
Ingo Molnar <mingo@...nel.org>,
"H . Peter Anvin" <hpa@...or.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Josh Poimboeuf <jpoimboe@...hat.com>
Subject: Re: [PATCH -tip v2] x86/percpu: Introduce const-qualified
const_pcpu_hot
> On Oct 21, 2023, at 5:36 PM, Uros Bizjak <ubizjak@...il.com> wrote:
>
> Some variables in pcpu_hot, currently current_task and top_of_stack
> are actually per-thread variables implemented as per-cpu variables
> and thus stable for the duration of the respective task
LGTM!
Powered by blists - more mailing lists