From: Yang Shi <yang.shi@windriver.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
<tglx@linutronix.de>, <rostedt@goodmis.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-rt-users@vger.kernel.org>
Subject: Re: [v4.4-rt PATCH] rt: trace: add rcuidle version macro for preemptirqsoff_hist and hrtimer_interrupt
Date: Wed, 9 Mar 2016 00:23:14 -0800 [thread overview]
Message-ID: <56DFDD72.5020807@windriver.com> (raw)
In-Reply-To: <56DE88FC.5080500@linutronix.de>
On 3/8/2016 12:10 AM, Sebastian Andrzej Siewior wrote:
> On 03/08/2016 12:45 AM, Yang Shi wrote:
>> diff --git a/include/trace/events/hist.h b/include/trace/events/hist.h
>> index 6122e42..37f6eb8 100644
>> --- a/include/trace/events/hist.h
>> +++ b/include/trace/events/hist.h
>> @@ -9,6 +9,7 @@
>>
>> #if !defined(CONFIG_PREEMPT_OFF_HIST) && !defined(CONFIG_INTERRUPT_OFF_HIST)
>> #define trace_preemptirqsoff_hist(a, b)
>> +#define trace_preemptirqsoff_hist_rcuidle(a, b)
>> #else
>> TRACE_EVENT(preemptirqsoff_hist,
> I have this piece already in my tree.
>
>>
>> @@ -33,6 +34,7 @@ TRACE_EVENT(preemptirqsoff_hist,
>>
>> #ifndef CONFIG_MISSED_TIMER_OFFSETS_HIST
>> #define trace_hrtimer_interrupt(a, b, c, d)
>> +#define trace_hrtimer_interrupt_rcuidle(a, b, c, d)
>> #else
>> TRACE_EVENT(hrtimer_interrupt,
> I was thinking about this but then I saw no users of it. Do we have
> any? (haven't seen them in v4.1 either).
AFAIK, no users. It got brought in by the forward port of 4.1 patch. We
could remove it.
Thanks,
Yang
>
> Sebastian
>
prev parent reply other threads:[~2016-03-09 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 23:45 [v4.4-rt PATCH] rt: trace: add rcuidle version macro for preemptirqsoff_hist and hrtimer_interrupt Yang Shi
2016-03-08 8:10 ` Sebastian Andrzej Siewior
2016-03-08 19:17 ` Steven Rostedt
2016-03-09 14:46 ` Sebastian Andrzej Siewior
2016-03-09 15:08 ` Steven Rostedt
2016-03-09 8:23 ` Yang Shi [this message]
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=56DFDD72.5020807@windriver.com \
--to=yang.shi@windriver.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).