Ming Lei, Thomas,
Sorry if it is a bit late to jump in.
On Mon, Aug 22, 2011 at 10:27 AM, Thomas Renninger tr...@suse.de wrote:
On Saturday, August 20, 2011 04:40:09 AM Ming Lei wrote:
Hi,
2011/8/20 Thomas Renninger tr...@suse.de:
On Friday, August 19, 2011 05:04:04 PM
Hi,
On Fri, Sep 2, 2011 at 3:26 PM, Jean Pihet jean.pi...@newoldbits.com wrote:
It was known that cpu_id is always the current cpu with current
implementation when this got introduced.
But the perf events API must not change back and forth for userspace
compatibility. Therefore the cpu_id was
On Saturday, August 20, 2011 04:40:09 AM Ming Lei wrote:
Hi,
2011/8/20 Thomas Renninger tr...@suse.de:
On Friday, August 19, 2011 05:04:04 PM tom.leim...@gmail.com wrote:
From: Ming Lei tom.leim...@gmail.com
This patch removes the 'cpu_id' parameter of the cpu_idle
trace point, based
From: Ming Lei tom.leim...@gmail.com
This patch removes the 'cpu_id' parameter of the cpu_idle
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
-
On Friday, August 19, 2011 05:04:04 PM tom.leim...@gmail.com wrote:
From: Ming Lei tom.leim...@gmail.com
This patch removes the 'cpu_id' parameter of the cpu_idle
trace point, based on the ideas below:
- the cpu_id which is passed to trace point is always the current
cpu
Are you sure
Hi,
2011/8/20 Thomas Renninger tr...@suse.de:
On Friday, August 19, 2011 05:04:04 PM tom.leim...@gmail.com wrote:
From: Ming Lei tom.leim...@gmail.com
This patch removes the 'cpu_id' parameter of the cpu_idle
trace point, based on the ideas below:
- the cpu_id which is passed to trace
