linux-kernel - Re: [PATCH 4/7] tracing: timer: Add deferrable flag to timer

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]

Message-ID: <20150524062043.GA13305@gmail.com>
Date:	Sun, 24 May 2015 08:20:43 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	John Stultz <john.stultz@...aro.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Badhri Jagan Sridharan <badhri@...gle.com>
Subject: Re: [PATCH 4/7] tracing: timer: Add deferrable flag to timer_start


* Ingo Molnar <mingo@...nel.org> wrote:

> > [...] So the field size is available for the tool. If the tool 
> > blindly applies the format string, it's hardly a fault of the 
> > kernel. And there is no point to bloat 32bit tracing with 64bit 
> > entries just because some random tool might be stupid.
> 
> Yeah, in a perfect world and so we could define arbitrarily complex 
> interfaces and expect tooling to follow it.

OTOH, on a second thought, libtraceevent handles this correctly, so 
the chance for tooling to get this wrong is much smaller than for 
other ABIs.

Plus the advantages on 32-bit systems you mentioned are real as well - 
so I concur with you.

Thanks,

	Ingo
--
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/