linux-kernel - Re: [PATCH 1/3] trace points: power: remove 'cpu_id' from trace_clock

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]

Message-ID: <1313766840.15704.104.camel@gandalf.stny.rr.com>
Date:	Fri, 19 Aug 2011 11:14:00 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	tom.leiming@...il.com
Cc:	fweisbec@...il.com, jean.pihet@...oldbits.com, mingo@...hat.com,
	trenn@...e.de, linux-kernel@...r.kernel.org,
	linux-omap@...r.kernel.org,
	Arjan van de Ven <arjan@...ux.intel.com>
Subject: Re: [PATCH 1/3] trace points: power: remove 'cpu_id' from
 trace_clock_*

On Fri, 2011-08-19 at 23:04 +0800, tom.leiming@...il.com wrote:
> From: Ming Lei <tom.leiming@...il.com>
> 
> This patch removes the 'cpu_id' parameter of the clock_*
> trace point, based on the ideas below:
> 
> - the cpu_id which is passed to trace point is always the current
>   cpu
> - the current cpu info has been included into the trace result already
> - smp_processor_id() can't be used safely in preemptible context.
> 

Do you know if these changes wont break powertop?

-- Steve


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