linux-kernel - Re: [PATCH 10/11] perf intel-pt: Add support for decoding FUP/TIP only

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: <20200709175506.GD1126680@tassilo.jf.intel.com>
Date:   Thu, 9 Jul 2020 10:55:06 -0700
From:   Andi Kleen <ak@...ux.intel.com>
To:     Adrian Hunter <adrian.hunter@...el.com>
Cc:     Arnaldo Carvalho de Melo <acme@...nel.org>,
        Jiri Olsa <jolsa@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 10/11] perf intel-pt: Add support for decoding FUP/TIP
 only

On Thu, Jul 09, 2020 at 08:36:27PM +0300, Adrian Hunter wrote:
> +The q option does not decode TNT packets, and does not walk object code, but
> +gets the ip from FUP and TIP packets.  The q option can be used with the b and i
> +options but the period is not used.  The q option decodes more quickly, but is
> +useful only if the control flow of interest is represented or indicated by FUP,
> +TIP, TIP.PGE, or TIP.PGD packets.  However the q option could be used to find
> +time ranges that could then be decoded fully using the --time option.

Ah ok the documentation is here. Ignore previous suggestion.

Can you describe the effect in a high level without referring to packet names?

The user may not be familar with them.

So two qs will be PSB only decoding I hope?

-Andi