[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230222173654.275a2c78@gandalf.local.home>
Date: Wed, 22 Feb 2023 17:36:54 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Dave Hansen <dave.hansen@...el.com>
Cc: "Joseph, Jithu" <jithu.joseph@...el.com>, hdegoede@...hat.com,
markgross@...nel.org, tglx@...utronix.de, mingo@...hat.com,
bp@...en8.de, dave.hansen@...ux.intel.com, x86@...nel.org,
hpa@...or.com, gregkh@...uxfoundation.org, ashok.raj@...el.com,
tony.luck@...el.com, linux-kernel@...r.kernel.org,
platform-driver-x86@...r.kernel.org, patches@...ts.linux.dev,
ravi.v.shankar@...el.com, thiago.macieira@...el.com,
athenas.jimenez.gonzalez@...el.com, sohil.mehta@...el.com
Subject: Re: [PATCH v2 4/7] platform/x86/intel/ifs: Implement Array BIST
test
On Wed, 22 Feb 2023 14:28:55 -0800
Dave Hansen <dave.hansen@...el.com> wrote:
> On 2/22/23 14:07, Joseph, Jithu wrote:
> > Since the trace has to be explicitly enabled (I thought it is okay to
> > add a more convenient custom one only to be enabled for detailed
> > analysis when required).
>
> man perf-script
Or do it in C with tracefs :-)
https://www.trace-cmd.org/Documentation/libtracefs/
-- Steve
>
> You should be able to write one to do exactly what you need in about 10
> minutes. No new tracepoints, no new kernel code to maintain. Knock
> yourself out with whatever conveniences you want. Just do it in userspace.
>
> I still think this patch should go away.
Powered by blists - more mailing lists