Re: [tip:perf/core] perf/ftrace: Optimize perf/tracepoint interaction for single events
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip:perf/core] perf/ftrace: Optimize perf/tracepoint interaction for single events
- From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
- Date: Wed, 19 May 2010 10:31:25 +0200
- Cc: mingo@xxxxxxxxxx, hpa@xxxxxxxxx, paulus@xxxxxxxxx, acme@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, efault@xxxxxx, rostedt@xxxxxxxxxxx, tglx@xxxxxxxxxxxxx, mingo@xxxxxxx, linux-tip-commits@xxxxxxxxxxxxxxx
- In-reply-to: <20100519082335.GG5704@nowhere>
- References: <tip-4f41c013f553957765902fb01475972f0af3e8e7@xxxxxxxxxxxxxx> <20100519075804.GF5704@nowhere> <1274257123.5605.10260.camel@twins> <20100519082335.GG5704@nowhere>
On Wed, 2010-05-19 at 10:23 +0200, Frederic Weisbecker wrote:
> Yeah, then if you launch perf sched for example, you'll have NR_CPU perf events
> attached to each lock trace events, since we create one event per cpu.
Right, but simple per task (non-inherited) would have only 1.
But yeah, plenty of room to improve here.
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]
