From: Peter Zijlstra <peterz@infradead.org>
To: Daniel Bristot de Oliveira <bristot@redhat.com>
Cc: linux-kernel@vger.kernel.org, williams@redhat.com,
daniel@bristot.me,
"Steven Rostedt (VMware)" <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Matthias Kaehlcke <mka@chromium.org>,
"Joel Fernandes (Google)" <joel@joelfernandes.org>,
Frederic Weisbecker <frederic@kernel.org>,
Yangtao Li <tiny.windzz@gmail.com>,
Tommaso Cucinotta <tommaso.cucinotta@santannapisa.it>
Subject: Re: [RFC 3/3] preempt_tracer: Use a percpu variable to control traceble calls
Date: Wed, 29 May 2019 10:41:18 +0200 [thread overview]
Message-ID: <20190529084118.GG2623@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <9b0698774be3bb406e2b8b2c12dc1fb91532bff0.1559051152.git.bristot@redhat.com>
On Tue, May 28, 2019 at 05:16:24PM +0200, Daniel Bristot de Oliveira wrote:
> #if defined(CONFIG_PREEMPT) && (defined(CONFIG_DEBUG_PREEMPT) || \
> defined(CONFIG_TRACE_PREEMPT_TOGGLE))
> +
> +DEFINE_PER_CPU(int, __traced_preempt_count) = 0;
> /*
> * If the value passed in is equal to the current preempt count
> * then we just disabled preemption. Start timing the latency.
> */
> void preempt_latency_start(int val)
> {
> - if (preempt_count() == val) {
> + int curr = this_cpu_read(__traced_preempt_count);
We actually have this_cpu_add_return();
> +
> + if (!curr) {
> unsigned long ip = get_lock_parent_ip();
> #ifdef CONFIG_DEBUG_PREEMPT
> current->preempt_disable_ip = ip;
> #endif
> trace_preempt_off(CALLER_ADDR0, ip);
> }
> +
> + this_cpu_write(__traced_preempt_count, curr + val);
> }
>
> static inline void preempt_add_start_latency(int val)
> @@ -3200,8 +3206,12 @@ NOKPROBE_SYMBOL(preempt_count_add);
> */
> void preempt_latency_stop(int val)
> {
> - if (preempt_count() == val)
> + int curr = this_cpu_read(__traced_preempt_count) - val;
this_cpu_sub_return();
> +
> + if (!curr)
> trace_preempt_on(CALLER_ADDR0, get_lock_parent_ip());
> +
> + this_cpu_write(__traced_preempt_count, curr);
> }
Can't say I love this, but it is miles better than the last patch.
next prev parent reply other threads:[~2019-05-29 8:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 15:16 [RFC 0/3] preempt_tracer: Fix preempt_disable tracepoint Daniel Bristot de Oliveira
2019-05-28 15:16 ` [RFC 1/3] softirq: Use preempt_latency_stop/start to trace preemption Daniel Bristot de Oliveira
2019-05-29 8:29 ` Peter Zijlstra
2019-05-29 9:30 ` Joel Fernandes
2019-05-29 12:22 ` Steven Rostedt
2019-06-04 10:39 ` Daniel Bristot de Oliveira
2019-06-04 12:01 ` Steven Rostedt
2019-05-28 15:16 ` [RFC 2/3] preempt_tracer: Disable IRQ while starting/stopping due to a preempt_counter change Daniel Bristot de Oliveira
2019-05-29 8:33 ` Peter Zijlstra
2019-05-29 9:40 ` Daniel Bristot de Oliveira
2019-05-29 10:20 ` Peter Zijlstra
2019-05-29 12:39 ` Steven Rostedt
2019-05-29 13:19 ` Peter Zijlstra
2019-05-29 13:29 ` Peter Zijlstra
2019-05-29 13:42 ` Steven Rostedt
2019-05-29 13:49 ` Peter Zijlstra
2019-05-29 13:58 ` Steven Rostedt
2019-05-29 13:51 ` Daniel Bristot de Oliveira
2019-05-29 18:21 ` Peter Zijlstra
2019-06-04 10:20 ` Daniel Bristot de Oliveira
2019-05-31 7:47 ` Joel Fernandes
2019-06-04 10:12 ` Daniel Bristot de Oliveira
2019-06-04 15:01 ` Steven Rostedt
2019-06-05 15:16 ` Joel Fernandes
2019-05-28 15:16 ` [RFC 3/3] preempt_tracer: Use a percpu variable to control traceble calls Daniel Bristot de Oliveira
2019-05-29 8:41 ` Peter Zijlstra [this message]
2019-05-29 9:48 ` Daniel Bristot de Oliveira
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=20190529084118.GG2623@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bristot@redhat.com \
--cc=daniel@bristot.me \
--cc=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mka@chromium.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tiny.windzz@gmail.com \
--cc=tommaso.cucinotta@santannapisa.it \
--cc=williams@redhat.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: 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