linux-kernel - Re: [PATCH 2/3] perf/x86/intel/pt: Add an option to not force PSB+ on every schedule-in

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: <87mvydkbrp.fsf@ashishki-desk.ger.corp.intel.com>
Date:	Thu, 30 Jul 2015 16:36:42 +0300
From:	Alexander Shishkin <alexander.shishkin@...ux.intel.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
	adrian.hunter@...el.com, x86@...nel.org, hpa@...or.com,
	acme@...radead.org
Subject: Re: [PATCH 2/3] perf/x86/intel/pt: Add an option to not force PSB+ on every schedule-in

Alexander Shishkin <alexander.shishkin@...ux.intel.com> writes:

> It kinda does make a difference: inside PSB+ you get a TSC packet, which
> carries the tsc timestamp as a payload, so, with the current behavior,
> since you'll get one of those at every event schedule-in, you'll have
> many more time synchronization points with the perf stream, but when the
> default changes, suddenly your timestamps way further apart and the
> decoder needs to put in additional guesswork to correlate those MMAP
> events in the perf stream with the PT trace.

I spoke hastily, TSC packets will be generated on every schedule-in (as
well as other packets that normally come in PSB+) regardless of the
actual PSB, so scratch the above. Let me replace the above with a
smaller patch.

Regards,
--
Alex
--
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/