From: Peter Zijlstra <peterz@infradead.org>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Qais Yousef <qais.yousef@arm.com>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Delyan Kratunov <delyank@fb.com>,
Namhyung Kim <namhyung@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
"bigeasy@linutronix.de" <bigeasy@linutronix.de>,
"dietmar.eggemann@arm.com" <dietmar.eggemann@arm.com>,
"keescook@chromium.org" <keescook@chromium.org>,
"x86@kernel.org" <x86@kernel.org>,
"andrii@kernel.org" <andrii@kernel.org>,
"u.kleine-koenig@pengutronix.de" <u.kleine-koenig@pengutronix.de>,
"vincent.guittot@linaro.org" <vincent.guittot@linaro.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"mingo@kernel.org" <mingo@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rdunlap@infradead.org" <rdunlap@infradead.org>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"Kenta.Tada@sony.com" <Kenta.Tada@sony.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"bristot@redhat.com" <bristot@redhat.com>,
"ebiederm@xmission.com" <ebiederm@xmission.com>,
"ast@kernel.org" <ast@kernel.org>,
"legion@kernel.org" <legion@kernel.org>,
"adharmap@quicinc.com" <adharmap@quicinc.com>,
"valentin.schneider@arm.com" <valentin.schneider@arm.com>,
"ed.tsai@mediatek.com" <ed.tsai@mediatek.com>,
"juri.lelli@redhat.com" <juri.lelli@redhat.com>
Subject: Re: [PATCH] sched/tracing: append prev_state to tp args instead
Date: Tue, 10 May 2022 10:29:40 +0200 [thread overview]
Message-ID: <20220510082940.GA100765@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20220510070122.GJ76023@worktop.programming.kicks-ass.net>
On Tue, May 10, 2022 at 09:01:22AM +0200, Peter Zijlstra wrote:
> On Mon, May 09, 2022 at 12:32:31PM -0700, Andrii Nakryiko wrote:
> > So can this patch be applied, please, or it's a hard no?
>
> Sorry; I got distracted with other work. I'll grudingly apply the patch.
gcc-11-i386-allmodconfig [15:35] FAILED
| In file included from ../include/trace/define_custom_trace.h:55,
| from ../samples/trace_events/trace_custom_sched.h:96,
| from ../samples/trace_events/trace_custom_sched.c:24:
| ../samples/trace_events/./trace_custom_sched.h: In function ‘ftrace_test_custom_probe_sched_switch’:
| ../include/trace/trace_custom_events.h:178:42: error: passing argument 1 of ‘check_trace_callback_type_sched_switch’ from incompatible pointer type [-Werror=incompatible-pointer-types]
| 178 | check_trace_callback_type_##call(trace_custom_event_raw_event_##template); \
| | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| | |
| | void (*)(void *, bool, unsigned int, struct task_struct *, struct task_struct *) {aka void (*)(void *, _Bool, unsigned int, struct task_struct *, struct task_struct *)}
| ../include/trace/trace_custom_events.h:34:9: note: in expansion of macro ‘DEFINE_CUSTOM_EVENT’
| 34 | DEFINE_CUSTOM_EVENT(name, name, PARAMS(proto), PARAMS(args));
| | ^~~~~~~~~~~~~~~~~~~
| ../samples/trace_events/./trace_custom_sched.h:21:1: note: in expansion of macro ‘TRACE_CUSTOM_EVENT’
| 21 | TRACE_CUSTOM_EVENT(sched_switch,
| | ^~~~~~~~~~~~~~~~~~
| In file included from ../include/linux/trace_events.h:11,
| from ../samples/trace_events/trace_custom_sched.c:10:
| ../include/linux/tracepoint.h:279:49: note: expected ‘void (*)(void *, bool, struct task_struct *, struct task_struct *, unsigned int)’ {aka ‘void (*)(void *, _Bool, struct task_struct *, struct task_struct *, unsigned int)’} but argument is of type ‘void (*)(void *, bool, unsigned int, struct task_struct *, struct task_struct *)’ {aka ‘void (*)(void *, _Bool, unsigned int, struct task_struct *, struct task_struct *)’}
| 279 | check_trace_callback_type_##name(void (*cb)(data_proto)) \
| | ~~~~~~~^~~~~~~~~~~~~~~
| ../include/linux/tracepoint.h:419:9: note: in expansion of macro ‘__DECLARE_TRACE’
| 419 | __DECLARE_TRACE(name, PARAMS(proto), PARAMS(args), \
| | ^~~~~~~~~~~~~~~
| ../include/linux/tracepoint.h:553:9: note: in expansion of macro ‘DECLARE_TRACE’
| 553 | DECLARE_TRACE(name, PARAMS(proto), PARAMS(args))
| | ^~~~~~~~~~~~~
| ../include/trace/events/sched.h:222:1: note: in expansion of macro ‘TRACE_EVENT’
| 222 | TRACE_EVENT(sched_switch,
| | ^~~~~~~~~~~
| cc1: some warnings being treated as errors
| make[3]: *** [../scripts/Makefile.build:292: samples/trace_events/trace_custom_sched.o] Error 1
| make[3]: *** Waiting for unfinished jobs....
| make[2]: *** [../scripts/Makefile.build:555: samples/trace_events] Error 2
| make[1]: *** [/opt/buildbot/linux-2.6/Makefile:1834: samples] Error 2
| make[1]: *** Waiting for unfinished jobs....
| make: *** [Makefile:219: __sub-make] Error 2
`----
next prev parent reply other threads:[~2022-05-10 8:30 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 16:25 [PATCH v3 0/2] sched/tracing: sched_switch prev_state reported as TASK_RUNNING when it's not Valentin Schneider
2022-01-20 16:25 ` [PATCH v3 1/2] sched/tracing: Don't re-read p->state when emitting sched_switch event Valentin Schneider
2022-03-01 15:24 ` [tip: sched/core] " tip-bot2 for Valentin Schneider
2022-03-04 16:13 ` Valentin Schneider
2022-03-08 18:02 ` Qais Yousef
2022-03-08 18:10 ` Greg KH
2022-03-08 18:51 ` Qais Yousef
2022-04-09 23:38 ` Qais Yousef
2022-04-10 22:06 ` Qais Yousef
2022-04-10 23:22 ` Holger Hoffstätte
2022-04-11 7:18 ` Holger Hoffstätte
2022-04-11 7:28 ` Greg KH
2022-04-11 8:05 ` Holger Hoffstätte
2022-04-11 13:23 ` Greg KH
2022-04-11 13:22 ` Greg KH
2022-04-11 21:06 ` Qais Yousef
2022-01-20 16:25 ` [PATCH v3 2/2] sched/tracing: Report TASK_RTLOCK_WAIT tasks as TASK_UNINTERRUPTIBLE Valentin Schneider
2022-03-01 15:24 ` [tip: sched/core] " tip-bot2 for Valentin Schneider
2022-04-09 23:42 ` [PATCH v3 2/2] " Qais Yousef
2022-04-10 6:14 ` Greg KH
2022-04-10 22:13 ` Qais Yousef
2022-04-11 13:20 ` Greg KH
2022-04-11 20:18 ` Qais Yousef
2022-01-21 17:15 ` [PATCH v3 0/2] sched/tracing: sched_switch prev_state reported as TASK_RUNNING when it's not Steven Rostedt
2022-02-27 15:33 ` Peter Zijlstra
2022-04-21 22:12 ` [PATCH] sched/tracing: append prev_state to tp args instead Delyan Kratunov
2022-04-22 10:13 ` Valentin Schneider
2022-04-22 11:09 ` Peter Zijlstra
2022-04-22 15:55 ` Steven Rostedt
2022-04-22 16:54 ` Andrii Nakryiko
2022-04-22 16:37 ` Andrii Nakryiko
2022-04-22 17:22 ` Delyan Kratunov
2022-04-22 18:30 ` Alexei Starovoitov
2022-04-26 12:28 ` Peter Zijlstra
2022-04-26 14:09 ` Qais Yousef
2022-04-26 15:54 ` Andrii Nakryiko
2022-04-27 10:34 ` Qais Yousef
2022-04-27 18:17 ` Andrii Nakryiko
2022-04-27 20:32 ` Alexei Starovoitov
2022-04-28 10:02 ` Qais Yousef
2022-05-09 19:32 ` Andrii Nakryiko
2022-05-10 7:01 ` Peter Zijlstra
2022-05-10 8:29 ` Peter Zijlstra [this message]
2022-05-10 14:31 ` Steven Rostedt
2022-05-11 18:28 ` [PATCH v2] " Delyan Kratunov
2022-05-11 19:10 ` Steven Rostedt
2022-05-11 22:45 ` [tip: sched/urgent] sched/tracing: Append " tip-bot2 for Delyan Kratunov
2022-05-11 23:40 ` [PATCH v2] sched/tracing: append " Thomas Gleixner
2022-04-26 15:51 ` [PATCH] " Andrii Nakryiko
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=20220510082940.GA100765@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Kenta.Tada@sony.com \
--cc=acme@kernel.org \
--cc=adharmap@quicinc.com \
--cc=akpm@linux-foundation.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=bristot@redhat.com \
--cc=delyank@fb.com \
--cc=dietmar.eggemann@arm.com \
--cc=ebiederm@xmission.com \
--cc=ed.tsai@mediatek.com \
--cc=juri.lelli@redhat.com \
--cc=keescook@chromium.org \
--cc=legion@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=qais.yousef@arm.com \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.org \
--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