[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wjwuO8UVLP5N7972TmfVc+sYEekcnZMF4rQLr662j7oXQ@mail.gmail.com>
Date: Thu, 27 Mar 2025 15:19:40 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: linux-kernel@...r.kernel.org, Juergen Gross <jgross@...e.com>,
"H . Peter Anvin" <hpa@...or.com>, Peter Zijlstra <peterz@...radead.org>, Borislav Petkov <bp@...en8.de>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 00/41] Simplify, reorganize and clean up the x86 INT3
based batch-patching code (alternative.c)
On Thu, 27 Mar 2025 at 13:54, Ingo Molnar <mingo@...nel.org> wrote:
>
> The second part of the series simplifies and standardizes the SMP batch-patching
> data & types namespace, around the new tp_array* namespace:
>
> int3_patching_desc => [removed]
> temp_mm_state_t => [removed]
> try_get_desc() => [removed]
> put_desc() => [removed]
>
> tp_vec,tp_vec_nr => tp_array
> int3_refs => tp_array_refs
Honestly, I think "int3" is better than "tp" as a part of the name.
"tp" doesn't say _anything_ to me, even though I understand it is
short for "text poke". But if you want to say 'text_poke", please just
write it out.
At least "int3" has some meaning in x86 context, unlike "tp".
So please either write out "text_poke" and accept that the names are a
bit longer (but a lot more descriptive), or use "int3" if you want to
save some typing.
Linus
PS. The casual meaning "tp" has in English everyday language is short
for "toilet paper".
Powered by blists - more mailing lists