lkml.org 
[lkml]   [2013]   [Jun]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: [PATCH v13 3/3] trace,x86: Add irq vector tracepoints
Date
OK, I will rename  debug_stack_use_ctr to debug_idt_ctr.
Thanks.

Seiji

> -----Original Message-----
> From: Steven Rostedt [mailto:rostedt@goodmis.org]
> Sent: Tuesday, June 04, 2013 4:58 PM
> To: Seiji Aguchi
> Cc: H. Peter Anvin; linux-kernel@vger.kernel.org; x86@kernel.org; tglx@linutronix.de; mingo@elte.hu; bp@alien8.de; linux-
> edac@vger.kernel.org; tony.luck@intel.com; dle-develop@lists.sourceforge.net; Tomoki Sekiyama
> Subject: Re: [PATCH v13 3/3] trace,x86: Add irq vector tracepoints
>
> 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
>

\
 
 \ /
  Last update: 2013-06-04 23:41    [W:0.043 / U:0.496 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site