[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220420193839.6e9d810b@gandalf.local.home>
Date: Wed, 20 Apr 2022 19:38:39 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Tony Luck <tony.luck@...el.com>
Cc: 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, corbet@....net,
gregkh@...uxfoundation.org, andriy.shevchenko@...ux.intel.com,
jithu.joseph@...el.com, ashok.raj@...el.com,
dan.j.williams@...el.com, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, platform-driver-x86@...r.kernel.org,
patches@...ts.linux.dev, ravi.v.shankar@...el.com
Subject: Re: [PATCH v3 10/11] trace: platform/x86/intel/ifs: Add trace point
to track Intel IFS operations
On Tue, 19 Apr 2022 09:38:58 -0700
Tony Luck <tony.luck@...el.com> wrote:
> +TRACE_EVENT(ifs_status,
> +
> + TP_PROTO(union ifs_scan activate, union ifs_status status),
Really, you want to pass the structure in by value, so that we have two
copies? One to get to this function and then one to write to the ring
buffer?
-- Steve
> +
> + TP_ARGS(activate, status),
> +
> + TP_STRUCT__entry(
> + __field( u64, status )
> + __field( u8, start )
> + __field( u8, stop )
> + ),
> +
> + TP_fast_assign(
> + __entry->start = activate.start;
> + __entry->stop = activate.stop;
> + __entry->status = status.data;
> + ),
> +
> + TP_printk("start: %.2x, stop: %.2x, status: %llx",
> + __entry->start,
> + __entry->stop,
> + __entry->status)
> +);
> +
> +#endif /* _TRACE_IFS_H */
Powered by blists - more mailing lists