linux-kernel - RE: [PATCH v13 3/3] trace,x86: Add irq vector tracepoints

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 4 Jun 2013 21:01:09 +0000
From:	Seiji Aguchi <seiji.aguchi@....com>
To:	Steven Rostedt <rostedt@...dmis.org>
CC:	"H. Peter Anvin" <hpa@...or.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"x86@...nel.org" <x86@...nel.org>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"mingo@...e.hu" <mingo@...e.hu>, "bp@...en8.de" <bp@...en8.de>,
	"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
	"tony.luck@...el.com" <tony.luck@...el.com>,
	"dle-develop@...ts.sourceforge.net" 
	<dle-develop@...ts.sourceforge.net>,
	Tomoki Sekiyama <tomoki.sekiyama@....com>
Subject: RE: [PATCH v13 3/3] trace,x86: Add irq vector tracepoints

OK, I will rename  debug_stack_use_ctr to debug_idt_ctr.
Thanks.

Seiji

> -----Original Message-----
> From: Steven Rostedt [mailto:rostedt@...dmis.org]
> Sent: Tuesday, June 04, 2013 4:58 PM
> To: Seiji Aguchi
> Cc: H. Peter Anvin; linux-kernel@...r.kernel.org; x86@...nel.org; tglx@...utronix.de; mingo@...e.hu; bp@...en8.de; linux-
> edac@...r.kernel.org; tony.luck@...el.com; dle-develop@...ts.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
>