LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Joel Fernandes <joelaf@google.com> To: linux-kernel@vger.kernel.org Cc: Joel Fernandes <joelaf@google.com>, Steven Rostedt <rostedt@goodmis.org>, Peter Zilstra <peterz@infradead.org>, Ingo Molnar <mingo@redhat.com>, Mathieu Desnoyers <mathieu.desnoyers@efficios.com>, Tom Zanussi <tom.zanussi@linux.intel.com>, Namhyung Kim <namhyung@kernel.org> Subject: [PATCH v1 0/2] Improve preemptirq tracepoint usage Date: Tue, 13 Mar 2018 14:43:25 -0700 [thread overview] Message-ID: <20180313214327.37475-1-joelaf@google.com> (raw) Hi, These patches improve the design of preemptirq tracepoints, clean up several of the ifdeffery and overall makes the feature configuration cleaner and less confusing. It also uses the tracepoints infra for the lockdep hooks for irqs on/off thus making a central point for all users of the event (kernel/trace/trace_preemptirq.c). Patches based on v4.16-rc5. Changes since RFC [1]: - handle case where lockdep warnings occur in tracepoint code (2/2) - protect tracepoint probe registration in lockdep init by ifdef. Joel Fernandes (2): tracing: Improve design of preemptirq tracepoints and its users tracepoint: Prevent false-positive lockdep warnings include/linux/ftrace.h | 11 +- include/linux/irqflags.h | 11 +- include/linux/lockdep.h | 6 +- include/linux/preempt.h | 2 +- include/linux/tracepoint.h | 23 +++- include/trace/events/preemptirq.h | 23 ++-- init/main.c | 2 +- kernel/locking/lockdep.c | 31 ++--- kernel/sched/core.c | 2 +- kernel/trace/Kconfig | 19 ++- kernel/trace/Makefile | 2 +- kernel/trace/trace_irqsoff.c | 206 +++++++----------------------- kernel/trace/trace_preemptirq.c | 70 ++++++++++ 13 files changed, 191 insertions(+), 217 deletions(-) create mode 100644 kernel/trace/trace_preemptirq.c [1] https://patchwork.kernel.org/patch/10202163/ Cc: Steven Rostedt <rostedt@goodmis.org> Cc: Peter Zilstra <peterz@infradead.org> Cc: Ingo Molnar <mingo@redhat.com> Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com> Cc: Tom Zanussi <tom.zanussi@linux.intel.com> Cc: Namhyung Kim <namhyung@kernel.org> Signed-off-by: Joel Fernandes <joelaf@google.com> -- 2.16.2.660.g709887971b-goog
next reply other threads:[~2018-03-13 21:43 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-03-13 21:43 Joel Fernandes [this message] 2018-03-13 21:43 ` [PATCH v1 1/2] tracing: Improve design of preemptirq tracepoints and its users Joel Fernandes 2018-03-15 19:51 ` kbuild test robot 2018-03-15 20:19 ` Joel Fernandes 2018-03-16 3:13 ` kbuild test robot 2018-03-16 3:28 ` Joel Fernandes 2018-03-16 8:22 ` [tracing] b648360016: WARNING:at_kernel/locking/lockdep.c:#check_flags kernel test robot 2018-03-13 21:43 ` [PATCH v1 2/2] tracepoint: Prevent false-positive lockdep warnings Joel Fernandes
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=20180313214327.37475-1-joelaf@google.com \ --to=joelaf@google.com \ --cc=linux-kernel@vger.kernel.org \ --cc=mathieu.desnoyers@efficios.com \ --cc=mingo@redhat.com \ --cc=namhyung@kernel.org \ --cc=peterz@infradead.org \ --cc=rostedt@goodmis.org \ --cc=tom.zanussi@linux.intel.com \ /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: linkBe 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; as well as URLs for NNTP newsgroup(s).