From: Steven Rostedt <rostedt@goodmis.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "hdegoede@redhat.com" <hdegoede@redhat.com>,
"markgross@kernel.org" <markgross@kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"Joseph, Jithu" <jithu.joseph@intel.com>,
"Raj, Ashok" <ashok.raj@intel.com>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"patches@lists.linux.dev" <patches@lists.linux.dev>,
"Shankar, Ravi V" <ravi.v.shankar@intel.com>
Subject: Re: [PATCH v4 09/10] trace: platform/x86/intel/ifs: Add trace point to track Intel IFS operations
Date: Tue, 26 Apr 2022 22:42:24 -0400 [thread overview]
Message-ID: <20220426224224.597dd732@rorschach.local.home> (raw)
In-Reply-To: <YmiF6Rsy04pUHVQo@agluck-desk3.sc.intel.com>
On Tue, 26 Apr 2022 16:53:13 -0700
"Luck, Tony" <tony.luck@intel.com> wrote:
>
> I looked at the examples in samples/trace_events/trace-events-sample.h
> and tried to use this. But I'm doing something wrong because the
> compiler barfs on something defined but not used.
>
> Maybe my problem is the TP_printk() in the DECLARE_EVENT_CLASS() that
> is over-ridden by DEFINE_EVENT_PRINT(). I wasn't at all sure what to
> put here ... or how to use the base tracepoint that doesn't have the
> printk() over-ridden.
Yeah, that could be confusing.
Basically, TRACE_EVENT() is simply defined as:
DECLARE_EVENT_CLASS()
DEFINE_EVENT();
So technically you could create the class and event with the same name,
and then you could create a second event on top of that. But I usually
suggest people explicitly specify the DECLARE_EVENT_CLASS() and
DEFINE_EVENT().
I would not do this until you have more than one event. The what you
would do is create one event where the print matches the
DECLARE_EVENT_CLASS() TP_printk(), and have that event defined with
just DEFINE_EVENT(). Then create other events with the
DEFINE_EVENT_PRINT().
>
> I think I need my class to just save both the u64 values to the trace
> buffer. Then the different trace points will extract the bits they want
> and print in a user friendly way. While this increases space used in
> the trace buffer, these events are not crazy high frequency. Usually
> one or two events per core with a gap 30 minutes or more between tests.
>
> In my ".c" file the tracepoint looks like this using the name from
> DEFINE_EVENT_PRINT(), and now passing the full u64 values:
>
> trace_ifs_status_saf(activate.data, status.data);
>
> and my #include file looks like this:
>
> ----------------------------------------------
> /* SPDX-License-Identifier: GPL-2.0 */
> #undef TRACE_SYSTEM
> #define TRACE_SYSTEM intel_ifs
>
> #if !defined(_TRACE_IFS_H) || defined(TRACE_HEADER_MULTI_READ)
> #define _TRACE_IFS_H
>
> #include <linux/ktime.h>
> #include <linux/tracepoint.h>
>
> DECLARE_EVENT_CLASS(ifs_status,
>
> TP_PROTO(u64 activate, u64 status),
>
> TP_ARGS(activate, status),
>
> TP_STRUCT__entry(
> __field( u64, activate )
> __field( u64, status )
> ),
>
> TP_fast_assign(
> __entry->activate = activate;
> __entry->status = status;
> ),
>
> TP_printk("activate: %llx status: %llx",
> __entry->activate,
> __entry->status)
> );
>
> DEFINE_EVENT_PRINT(ifs_status, ifs_status_saf,
> TP_PROTO(u64 activate, u64 status),
> TP_ARGS(activate, status),
> TP_printk("start: %.2x, stop: %.2x, status: %llx",
> ((union ifs_scan *)&(__entry->activate))->start,
> ((union ifs_scan *)&(__entry->activate))->stop,
> __entry->status)
> );
>
> #endif /* _TRACE_IFS_H */
>
> /* This part must be outside protection */
> #include <trace/define_trace.h>
> -----------------------------------------------------
>
> GCC messages:
>
>
> CC [M] drivers/platform/x86/intel/ifs/runtest.o
> In file included from /home/agluck/GIT/mywork/include/trace/define_trace.h:102,
> from /home/agluck/GIT/mywork/include/trace/events/intel_ifs.h:44,
> from /home/agluck/GIT/mywork/drivers/platform/x86/intel/ifs/runtest.c:27:
> /home/agluck/GIT/mywork/include/trace/trace_events.h:426:13: warning: ‘print_fmt_ifs_status’ defined but not used [-Wunused-variable]
> 426 | static char print_fmt_##call[] = print; \
> | ^~~~~~~~~~
> /home/agluck/GIT/mywork/include/trace/events/intel_ifs.h:11:1: note: in expansion of macro ‘DECLARE_EVENT_CLASS’
> 11 | DECLARE_EVENT_CLASS(ifs_status,
> | ^~~~~~~~~~~~~~~~~~~
> In file included from /home/agluck/GIT/mywork/include/trace/define_trace.h:102,
> from /home/agluck/GIT/mywork/include/trace/events/intel_ifs.h:44,
> from /home/agluck/GIT/mywork/drivers/platform/x86/intel/ifs/runtest.c:27:
> /home/agluck/GIT/mywork/include/trace/trace_events.h:207:37: warning: ‘trace_event_type_funcs_ifs_status’ defined but not used [-Wunused-variable]
> 207 | static struct trace_event_functions trace_event_type_funcs_##call = { \
> | ^~~~~~~~~~~~~~~~~~~~~~~
> /home/agluck/GIT/mywork/include/trace/events/intel_ifs.h:11:1: note: in expansion of macro ‘DECLARE_EVENT_CLASS’
> 11 | DECLARE_EVENT_CLASS(ifs_status,
> | ^~~~~~~~~~~~~~~~~~~
> make[1]: Leaving directory '/home/agluck/GIT/mywork/build/ifsv5-rc1'
>
Yeah, because you don't have more than one event, so the
DEFINE_EVENT_PRINT() does not make sense. You still need one
DEFINE_EVENT() otherwise, you will get that static function not used
warning.
-- Steve
next prev parent reply other threads:[~2022-04-27 2:42 UTC|newest]
Thread overview: 152+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 19:13 [PATCH v2 00/10] Introduce In Field Scan driver Jithu Joseph
2022-04-07 19:13 ` [PATCH v2 01/10] x86/microcode/intel: expose collect_cpu_info_early() for IFS Jithu Joseph
2022-04-08 8:34 ` Borislav Petkov
2022-04-21 14:56 ` Thomas Gleixner
2022-04-07 19:13 ` [PATCH v2 02/10] Documentation: In-Field Scan Jithu Joseph
2022-04-07 19:13 ` [PATCH v2 03/10] platform/x86/intel/ifs: Add driver for " Jithu Joseph
2022-04-07 19:13 ` [PATCH v2 04/10] platform/x86/intel/ifs: Load IFS Image Jithu Joseph
2022-04-08 5:02 ` Greg KH
2022-04-08 5:04 ` Greg KH
2022-04-07 19:13 ` [PATCH v2 05/10] platform/x86/intel/ifs: Check IFS Image sanity Jithu Joseph
2022-04-07 19:13 ` [PATCH v2 06/10] platform/x86/intel/ifs: Authenticate and copy to secured memory Jithu Joseph
2022-04-07 19:13 ` [PATCH v2 07/10] platform/x86/intel/ifs: Add scan test support Jithu Joseph
2022-04-07 19:13 ` [PATCH v2 08/10] platform/x86/intel/ifs: Add IFS sysfs interface Jithu Joseph
2022-04-08 4:59 ` Greg KH
2022-04-07 19:13 ` [PATCH v2 09/10] platform/x86/intel/ifs: add ABI documentation for IFS Jithu Joseph
2022-04-08 5:02 ` Greg KH
2022-04-07 19:13 ` [PATCH v2 10/10] trace: platform/x86/intel/ifs: Add trace point to track Intel IFS operations Jithu Joseph
2022-04-19 16:38 ` [PATCH v3 00/11] Introduce In Field Scan driver Tony Luck
2022-04-19 16:38 ` [PATCH v3 01/11] x86/microcode/intel: Expose collect_cpu_info_early() for IFS Tony Luck
2022-04-19 16:38 ` [PATCH v3 02/11] Documentation: In-Field Scan Tony Luck
2022-04-19 16:48 ` Greg KH
2022-04-19 19:45 ` Dan Williams
2022-04-20 7:48 ` Greg KH
2022-04-19 16:38 ` [PATCH v3 03/11] platform/x86/intel/ifs: Create device for Intel IFS (In Field Scan) Tony Luck
2022-04-19 16:47 ` Greg KH
2022-04-19 18:09 ` Dan Williams
2022-04-19 22:28 ` Dan Williams
2022-04-20 7:49 ` Greg KH
2022-04-20 7:48 ` Greg KH
2022-04-20 15:27 ` Luck, Tony
2022-04-20 17:46 ` Greg KH
2022-04-20 17:57 ` Luck, Tony
2022-04-20 18:04 ` Greg KH
2022-04-20 18:08 ` Luck, Tony
2022-04-20 19:04 ` Greg KH
2022-04-19 16:38 ` [PATCH v3 04/11] platform/x86/intel/ifs: Add stub driver for In-Field Scan Tony Luck
2022-04-19 16:38 ` [PATCH v3 05/11] platform/x86/intel/ifs: Read IFS firmware image Tony Luck
2022-04-19 17:14 ` Greg KH
2022-04-19 16:38 ` [PATCH v3 06/11] platform/x86/intel/ifs: Check IFS Image sanity Tony Luck
2022-04-19 17:16 ` Greg KH
2022-04-19 16:38 ` [PATCH v3 07/11] platform/x86/intel/ifs: Authenticate and copy to secured memory Tony Luck
2022-04-19 16:38 ` [PATCH v3 08/11] platform/x86/intel/ifs: Add scan test support Tony Luck
2022-04-19 16:38 ` [PATCH v3 09/11] platform/x86/intel/ifs: Add IFS sysfs interface Tony Luck
2022-04-19 17:20 ` Greg KH
2022-04-19 17:35 ` Luck, Tony
2022-04-19 17:58 ` Greg KH
2022-04-19 18:15 ` Dan Williams
2022-04-19 18:24 ` Dan Williams
2022-04-19 16:38 ` [PATCH v3 10/11] trace: platform/x86/intel/ifs: Add trace point to track Intel IFS operations Tony Luck
2022-04-20 23:38 ` Steven Rostedt
2022-04-21 4:26 ` Luck, Tony
2022-04-21 12:41 ` Steven Rostedt
2022-04-19 16:38 ` [PATCH v3 11/11] platform/x86/intel/ifs: add ABI documentation for IFS Tony Luck
2022-04-22 20:02 ` [PATCH v4 00/10] Introduce In Field Scan driver Tony Luck
2022-04-22 20:02 ` [PATCH v4 01/10] x86/microcode/intel: Expose collect_cpu_info_early() for IFS Tony Luck
2022-04-22 20:02 ` [PATCH v4 02/10] x86/msr-index: Define INTEGRITY_CAPABILITIES MSR Tony Luck
2022-04-22 20:02 ` [PATCH v4 03/10] platform/x86/intel/ifs: Add stub driver for In-Field Scan Tony Luck
2022-04-22 20:02 ` [PATCH v4 04/10] platform/x86/intel/ifs: Read IFS firmware image Tony Luck
2022-04-26 10:45 ` Greg KH
2022-04-26 16:12 ` Luck, Tony
2022-04-26 16:36 ` Greg KH
2022-04-26 18:47 ` Luck, Tony
2022-04-22 20:02 ` [PATCH v4 05/10] platform/x86/intel/ifs: Check IFS Image sanity Tony Luck
2022-04-22 20:02 ` [PATCH v4 06/10] platform/x86/intel/ifs: Authenticate and copy to secured memory Tony Luck
2022-04-22 20:02 ` [PATCH v4 07/10] platform/x86/intel/ifs: Add scan test support Tony Luck
2022-04-22 20:02 ` [PATCH v4 08/10] platform/x86/intel/ifs: Add IFS sysfs interface Tony Luck
2022-04-22 20:02 ` [PATCH v4 09/10] trace: platform/x86/intel/ifs: Add trace point to track Intel IFS operations Tony Luck
2022-04-25 14:52 ` Steven Rostedt
2022-04-25 16:49 ` Luck, Tony
2022-04-26 1:49 ` Steven Rostedt
2022-04-26 23:53 ` Luck, Tony
2022-04-27 2:42 ` Steven Rostedt [this message]
2022-04-22 20:02 ` [PATCH v4 10/10] platform/x86/intel/ifs: add ABI documentation for IFS Tony Luck
2022-04-28 15:38 ` [PATCH v5 00/10] Introduce In Field Scan driver Tony Luck
2022-04-28 15:38 ` [PATCH v5 01/10] x86/microcode/intel: Expose collect_cpu_info_early() for IFS Tony Luck
2022-05-03 15:29 ` Borislav Petkov
2022-05-04 10:28 ` Thomas Gleixner
2022-04-28 15:38 ` [PATCH v5 02/10] x86/msr-index: Define INTEGRITY_CAPABILITIES MSR Tony Luck
2022-04-28 15:38 ` [PATCH v5 03/10] platform/x86/intel/ifs: Add stub driver for In-Field Scan Tony Luck
2022-05-04 10:35 ` Thomas Gleixner
2022-05-04 16:24 ` Luck, Tony
2022-05-04 16:28 ` Borislav Petkov
2022-04-28 15:38 ` [PATCH v5 04/10] platform/x86/intel/ifs: Read IFS firmware image Tony Luck
2022-05-04 10:37 ` Thomas Gleixner
2022-05-04 16:49 ` Luck, Tony
2022-04-28 15:38 ` [PATCH v5 05/10] platform/x86/intel/ifs: Check IFS Image sanity Tony Luck
2022-04-28 15:38 ` [PATCH v5 06/10] platform/x86/intel/ifs: Authenticate and copy to secured memory Tony Luck
2022-05-04 10:48 ` Thomas Gleixner
2022-04-28 15:38 ` [PATCH v5 07/10] platform/x86/intel/ifs: Add scan test support Tony Luck
2022-05-04 12:29 ` Thomas Gleixner
2022-05-04 18:52 ` Luck, Tony
2022-05-04 23:15 ` Thomas Gleixner
2022-05-05 8:28 ` Peter Zijlstra
2022-05-05 9:01 ` Thomas Gleixner
2022-05-05 18:32 ` Luck, Tony
2022-05-05 20:21 ` Peter Zijlstra
2022-04-28 15:38 ` [PATCH v5 08/10] platform/x86/intel/ifs: Add IFS sysfs interface Tony Luck
2022-04-28 15:38 ` [PATCH v5 09/10] trace: platform/x86/intel/ifs: Add trace point to track Intel IFS operations Tony Luck
2022-04-28 15:38 ` [PATCH v5 10/10] platform/x86/intel/ifs: add ABI documentation for IFS Tony Luck
2022-04-28 15:58 ` [PATCH v5 00/10] Introduce In Field Scan driver Greg KH
2022-04-28 16:07 ` Luck, Tony
2022-05-02 15:15 ` Hans de Goede
2022-05-02 17:23 ` Luck, Tony
2022-05-03 15:32 ` Borislav Petkov
2022-05-03 16:04 ` Luck, Tony
2022-05-03 16:26 ` Luck, Tony
2022-05-06 14:19 ` Hans de Goede
2022-05-06 15:53 ` Luck, Tony
2022-05-06 18:41 ` Hans de Goede
2022-05-09 17:05 ` Luck, Tony
2022-05-09 18:12 ` Hans de Goede
2022-05-06 1:40 ` [PATCH v6 00/11] " Tony Luck
2022-05-06 1:40 ` [PATCH v6 01/11] x86/microcode/intel: Expose collect_cpu_info_early() for IFS Tony Luck
2022-05-06 1:40 ` [PATCH v6 02/11] x86/msr-index: Define INTEGRITY_CAPABILITIES MSR Tony Luck
2022-05-06 8:19 ` Thomas Gleixner
2022-05-06 1:40 ` [PATCH v6 03/11] stop_machine: Add stop_core_cpuslocked() for per-core operations Tony Luck
2022-05-06 8:20 ` Thomas Gleixner
2022-05-06 1:40 ` [PATCH v6 04/11] platform/x86/intel/ifs: Add stub driver for In-Field Scan Tony Luck
2022-05-06 8:23 ` Thomas Gleixner
2022-05-06 1:40 ` [PATCH v6 05/11] platform/x86/intel/ifs: Read IFS firmware image Tony Luck
2022-05-06 1:40 ` [PATCH v6 06/11] platform/x86/intel/ifs: Check IFS Image sanity Tony Luck
2022-05-06 1:40 ` [PATCH v6 07/11] platform/x86/intel/ifs: Authenticate and copy to secured memory Tony Luck
2022-05-06 1:40 ` [PATCH v6 08/11] platform/x86/intel/ifs: Add scan test support Tony Luck
2022-05-06 13:30 ` Thomas Gleixner
2022-05-06 18:49 ` Luck, Tony
2022-05-06 19:06 ` Thomas Gleixner
2022-05-06 1:40 ` [PATCH v6 09/11] platform/x86/intel/ifs: Add IFS sysfs interface Tony Luck
2022-05-06 1:40 ` [PATCH v6 10/11] trace: platform/x86/intel/ifs: Add trace point to track Intel IFS operations Tony Luck
2022-05-06 1:40 ` [PATCH v6 11/11] platform/x86/intel/ifs: add ABI documentation for IFS Tony Luck
2022-05-06 22:53 ` [PATCH v7 00/12] Introduce In Field Scan driver Tony Luck
2022-05-06 22:53 ` [PATCH v7 01/12] x86/microcode/intel: Expose collect_cpu_info_early() for IFS Tony Luck
2022-05-06 22:54 ` [PATCH v7 02/12] x86/msr-index: Define INTEGRITY_CAPABILITIES MSR Tony Luck
2022-05-06 22:54 ` [PATCH v7 03/12] stop_machine: Add stop_core_cpuslocked() for per-core operations Tony Luck
2022-05-06 22:54 ` [PATCH v7 04/12] platform/x86/intel/ifs: Add stub driver for In-Field Scan Tony Luck
2022-05-06 22:54 ` [PATCH v7 05/12] platform/x86/intel/ifs: Read IFS firmware image Tony Luck
2022-05-09 12:11 ` Thomas Gleixner
2022-05-06 22:54 ` [PATCH v7 06/12] platform/x86/intel/ifs: Check IFS Image sanity Tony Luck
2022-05-09 12:11 ` Thomas Gleixner
2022-05-09 16:31 ` Borislav Petkov
2022-05-09 16:51 ` Luck, Tony
2022-05-09 16:56 ` Borislav Petkov
2022-05-06 22:54 ` [PATCH v7 07/12] platform/x86/intel/ifs: Authenticate and copy to secured memory Tony Luck
2022-05-09 12:11 ` Thomas Gleixner
2022-05-06 22:54 ` [PATCH v7 08/12] platform/x86/intel/ifs: Add scan test support Tony Luck
2022-05-09 12:11 ` Thomas Gleixner
2022-05-06 22:54 ` [PATCH v7 09/12] platform/x86/intel/ifs: Add IFS sysfs interface Tony Luck
2022-05-09 12:12 ` Thomas Gleixner
2022-05-06 22:54 ` [PATCH v7 10/12] trace: platform/x86/intel/ifs: Add trace point to track Intel IFS operations Tony Luck
2022-05-06 22:54 ` [PATCH v7 11/12] platform/x86/intel/ifs: add ABI documentation for IFS Tony Luck
2022-05-06 22:54 ` [PATCH v7 12/12] Documentation: In-Field Scan Tony Luck
2022-05-09 12:16 ` Thomas Gleixner
2022-05-11 15:51 ` [PATCH v7 00/12] Introduce In Field Scan driver Hans de Goede
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=20220426224224.597dd732@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=hpa@zytor.com \
--cc=jithu.joseph@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=mingo@redhat.com \
--cc=patches@lists.linux.dev \
--cc=platform-driver-x86@vger.kernel.org \
--cc=ravi.v.shankar@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®