linux-kernel - Re: [PATCH v2 0/6] Add tracepoints to trace all system IRQs

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 28 Jul 2011 15:28:22 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Vaibhav Nagarnaik <vnagarnaik@...gle.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Michael Rubin <mrubin@...gle.com>,
	David Sharp <dhsharp@...gle.com>, linux-kernel@...r.kernel.org,
	x86@...nel.org
Subject: Re: [PATCH v2 0/6] Add tracepoints to trace all system IRQs

On Thu, 2011-07-28 at 15:09 +0200, Frederic Weisbecker wrote:
> On Thu, Jul 28, 2011 at 02:53:52PM +0200, Peter Zijlstra wrote:
> > On Thu, 2011-07-28 at 14:31 +0200, Frederic Weisbecker wrote:
> > > 
> > > Because that requires to put the tracepoints in every interrupt sources
> > > for every archs instead of putting one in the generic space. 
> > 
> > Yeah so, he needs to touch arch code anyway.
> 
> He needs to touch arch code for pure arch interrupts or some cases
> where we don't have the choice. But otherwise there are many
> cases where we can put that in the generic code.

Which I just pointed out you can't, some 'generic' handlers are in fact
multiplexed on a single arch interrupt. If you want all interrupts, use
pure arch hooks at the lowest level and stop mucking about.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/