linux-kernel - Re: [tip:perf/core] Revert "sched, perf: Use a single callback into the scheduler"

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: <1337790834.9783.30.camel@laptop>
Date:	Wed, 23 May 2012 18:33:54 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	mingo@...nel.org, hpa@...or.com, linux-kernel@...r.kernel.org,
	tglx@...utronix.de, jolsa@...hat.com
Cc:	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:perf/core] Revert "sched, perf: Use a single callback
 into the scheduler"

On Wed, 2012-05-23 at 09:09 -0700, tip-bot for Jiri Olsa wrote:
>  > I rather liked we could do away with both that black-spot and
>  > clean up the code a little, but apparently people rely on it.
> 
Ingo noted that inherited counters already are active over the context
switch (due to the lazy switch optimization) and thus profile the
context switch cost.

Regular per-task counters not including this are therefore not
consistent.

So it would be good to find a way to fix the tracing fallout
differently. A well..

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