[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250618143727.1a406e41@gandalf.local.home>
Date: Wed, 18 Jun 2025 14:37:27 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Peter Zijlstra <peterz@...radead.org>, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, bpf@...r.kernel.org, x86@...nel.org,
Masami Hiramatsu <mhiramat@...nel.org>, Mathieu Desnoyers
<mathieu.desnoyers@...icios.com>, Josh Poimboeuf <jpoimboe@...nel.org>,
Ingo Molnar <mingo@...nel.org>, Jiri Olsa <jolsa@...nel.org>, Namhyung Kim
<namhyung@...nel.org>, Thomas Gleixner <tglx@...utronix.de>, Andrii
Nakryiko <andrii@...nel.org>, Indu Bhagat <indu.bhagat@...cle.com>, "Jose
E. Marchesi" <jemarch@....org>, Beau Belgrave <beaub@...ux.microsoft.com>,
Jens Remus <jremus@...ux.ibm.com>, Andrew Morton
<akpm@...ux-foundation.org>
Subject: Re: [PATCH v10 03/14] unwind_user: Add compat mode frame pointer
support
On Wed, 18 Jun 2025 10:52:22 -0700
Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> In this case, I have to agree with PeterZ that this just looks odd:
>
> - if (get_user(ra, (unsigned long *)(cfa + frame->ra_off)))
> + if (UNWIND_GET_USER_LONG(ra, cfa + frame->ra_off, state))
>
> why is UNWIND_GET_USER_LONG() so loud when it just replaces "get_user()"?
>
> Note that "get_user()" itself is a macro, and is lower-case, even
> though you couldn't actually do it as a function (because it changes
> its first argument in place).
OK, I'll make it lower case.
Thanks!
-- Steve
Powered by blists - more mailing lists