linux-kernel - Re: [PATCH v2] trace: Add x86 irq vector entry/exit 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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 7 Jul 2011 01:56:16 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	David Sharp <dhsharp@...gle.com>,
	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>, x86@...nel.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Jiaying Zhang <jiayingz@...gle.com>
Subject: Re: [PATCH v2] trace: Add x86 irq vector entry/exit tracepoints

On Wed, Jul 06, 2011 at 04:43:23PM -0700, H. Peter Anvin wrote:
> On 06/15/2011 08:02 PM, Frederic Weisbecker wrote:
> > 
> > If a generic tracepoint can replace one per arch, we all want that instead.
> > This is 24 times (24 archs) less maintainance burden.
> > 
> 
> Are you in effect saying that tracepoints are now a stable ABI?  They
> sure as hell haven't been architected, reviewed, or accepted for any
> such purpose.

Nope, I'm rather suggesting that it's better to have 1 line of code instead of 24.

And even if tracepoints are not supposed to be stable ABI (I actually believe there
is no absolute answer to that, it depends on the tracepoint and on the context),
tools are much happier with a common tracepoint interface amongst archs.
--
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/