[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3E29A42D-8A6A-4342-8C60-2BEF1EDCD640@goodmis.org>
Date: Fri, 16 May 2025 10:42:48 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Will Deacon <will@...nel.org>, Nam Cao <namcao@...utronix.de>
CC: Gabriele Monaco <gmonaco@...hat.com>, linux-trace-kernel@...r.kernel.org,
linux-kernel@...r.kernel.org, john.ogness@...utronix.de,
Catalin Marinas <catalin.marinas@....com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v6 17/22] arm64: mm: Add page fault trace points
On May 16, 2025 10:04:50 AM EDT, Will Deacon <will@...nel.org> wrote:
>
>> + if (user_mode(regs))
>> + trace_page_fault_user(addr, regs, esr);
>> + else
>> + trace_page_fault_kernel(addr, regs, esr);
>
>Why is this after kprobe_page_fault()?
>
>It's also a shame that the RV monitor can't hook into perf, as we
>already have a sw event for page faults that you could use instead of
>adding something new.
>
Perf events work for perf only. My question is why isn't this a tracepoint that perf could hook into?
Tracepoints are made to be generic, whereas perf events are not.
-- Steve
Powered by blists - more mailing lists