From: Peter Zijlstra <peterz@infradead.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@redhat.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, H Peter Anvin <hpa@zytor.com>
Subject: Re: [PATCH V2 0/2] perf/x86/intel/pt: Add support for event tracing and TNT disabling
Date: Tue, 15 Feb 2022 16:35:02 +0100 [thread overview]
Message-ID: <YgvIJop34KuyUIx6@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20220126104815.2807416-1-adrian.hunter@intel.com>
On Wed, Jan 26, 2022 at 12:48:13PM +0200, Adrian Hunter wrote:
> Hi
>
> As of Intel SDM (https://www.intel.com/sdm) version 076, there are 2 new
> Intel PT features called Event Trace and TNT-Disable.
>
> Event Trace exposes details about asynchronous events such as interrupts
> and VM-Entry/Exit.
>
> TNT-Disable disables TNT packets to reduce the tracing overhead, but with
> the result that exact control flow information is lost.
What's a TNT?
next prev parent reply other threads:[~2022-02-15 15:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 10:48 [PATCH V2 0/2] perf/x86/intel/pt: Add support for event tracing and TNT disabling Adrian Hunter
2022-01-26 10:48 ` [PATCH V2 1/2] perf/x86/intel/pt: Add a capability and config bit for event tracing Adrian Hunter
2022-02-16 14:57 ` [tip: perf/core] " tip-bot2 for Alexander Shishkin
2022-01-26 10:48 ` [PATCH V2 2/2] perf/x86/intel/pt: Add a capability and config bit for disabling TNTs Adrian Hunter
2022-02-16 14:57 ` [tip: perf/core] " tip-bot2 for Alexander Shishkin
2022-02-08 6:28 ` [PATCH V2 0/2] perf/x86/intel/pt: Add support for event tracing and TNT disabling Adrian Hunter
2022-02-15 14:18 ` Adrian Hunter
2022-02-15 15:35 ` Peter Zijlstra [this message]
2022-02-15 15:40 ` Adrian Hunter
2022-02-15 15:51 ` Peter Zijlstra
2022-02-15 15:41 ` Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YgvIJop34KuyUIx6@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.