From: Helge Deller <deller@gmx.de>
To: Josh Poimboeuf <jpoimboe@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Cc: "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
linux-kernel@vger.kernel.org,
Sven Schnelle <svens@stackframe.org>,
linux-trace-kernel@vger.kernel.org, linux-parisc@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] parisc/ftrace: Fix function graph tracing disablement
Date: Thu, 10 Oct 2024 22:25:13 +0200 [thread overview]
Message-ID: <f2dd3a74-cd3d-4277-904d-223a8b393d56@gmx.de> (raw)
In-Reply-To: <20241010195610.25mraxgovi4vowo2@treble>
On 10/10/24 21:56, Josh Poimboeuf wrote:
> On Thu, Oct 10, 2024 at 03:48:40PM -0400, Steven Rostedt wrote:
>>> +++ b/arch/parisc/kernel/ftrace.c
>>> @@ -87,7 +87,7 @@ int ftrace_enable_ftrace_graph_caller(void)
>>>
>>> int ftrace_disable_ftrace_graph_caller(void)
>>> {
>>> - static_key_enable(&ftrace_graph_enable.key);
>>> + static_key_disable(&ftrace_graph_enable.key);
>>> return 0;
>>> }
>>> #endif
>>
>> Awfully quite :-/
>>
>> I wonder if anyone cares about parisc today?
Actually I do, and yes we have users.
Of course in reality that's "fun" users and not "productive" usage.
From programming perspective parisc is quite interesting since it
has an upwards-growing stack, limited ways of atomic ops,
and some awkward cache dependencies, so I regularly find
issues in generic Linux code which would not be found otherwise.
> I still see some git activity in arch/parisc, so apparently so...
>
> I only stumbled on this by accident (code inspection) while making
> another unrelated change.
Thanks for your patch!
I'll apply it in my for-next git tree and push upstream at some point
(unless someone else takes it before me).
Helge
next prev parent reply other threads:[~2024-10-10 20:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 21:32 [PATCH] parisc/ftrace: Fix function graph tracing disablement Josh Poimboeuf
2024-10-10 19:48 ` Steven Rostedt
2024-10-10 19:56 ` Josh Poimboeuf
2024-10-10 20:25 ` Helge Deller [this message]
2024-10-10 20:33 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f2dd3a74-cd3d-4277-904d-223a8b393d56@gmx.de \
--to=deller@gmx.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=svens@stackframe.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox