From: Steven Rostedt <rostedt@goodmis.org>
To: Seiji Aguchi <seiji.aguchi@hds.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@elte.hu" <mingo@elte.hu>, "bp@alien8.de" <bp@alien8.de>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"tony.luck@intel.com" <tony.luck@intel.com>,
"dle-develop@lists.sourceforge.net"
<dle-develop@lists.sourceforge.net>,
Tomoki Sekiyama <tomoki.sekiyama@hds.com>
Subject: Re: [PATCH v13 3/3] trace,x86: Add irq vector tracepoints
Date: Tue, 04 Jun 2013 16:58:09 -0400 [thread overview]
Message-ID: <1370379489.9844.7.camel@gandalf.local.home> (raw)
In-Reply-To: <A5ED84D3BB3A384992CBB9C77DEDA4D41B011681@USINDEM103.corp.hds.com>
On Tue, 2013-06-04 at 20:20 +0000, Seiji Aguchi wrote:
> Steven,
>
> >
> > Hmm, maybe we can do it. Have two counters, a debug_idt_ctr and a
> > trace_idt_ctr, then have a function that basically does this:
> >
> > if (this_cpu_read(debug_idt_ctr))
>
> I think we can use "debug_stack_use_ctr" for the checking.
> Is it correct?
> Or, do I need to introduce a new debug_idt_ctr?
>
No, it's the same variable. I was thinking we should rename it too, as
debug_stack_use_ctr, doesn't really describe what is happening anymore.
-- Steve
next prev parent reply other threads:[~2013-06-04 20:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 19:25 [PATCH v13 0/3]trace,x86: irq vector tracepoint support Seiji Aguchi
2013-06-03 19:28 ` [PATCH v13 1/3] tracing: Add DEFINE_EVENT_FN() macro Seiji Aguchi
2013-06-03 19:29 ` [PATCH v13 2/3] trace,x86: Introduce entering/exiting_irq() Seiji Aguchi
2013-06-03 19:29 ` [PATCH v13 3/3] trace,x86: Add irq vector tracepoints Seiji Aguchi
2013-06-03 23:53 ` Steven Rostedt
2013-06-04 15:50 ` Seiji Aguchi
2013-06-04 18:15 ` H. Peter Anvin
2013-06-04 18:32 ` Steven Rostedt
2013-06-04 18:37 ` Seiji Aguchi
2013-06-04 20:20 ` Seiji Aguchi
2013-06-04 20:58 ` Steven Rostedt [this message]
2013-06-04 21:01 ` Seiji Aguchi
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=1370379489.9844.7.camel@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bp@alien8.de \
--cc=dle-develop@lists.sourceforge.net \
--cc=hpa@zytor.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=seiji.aguchi@hds.com \
--cc=tglx@linutronix.de \
--cc=tomoki.sekiyama@hds.com \
--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®