From: kan.liang@linux.intel.com
To: peterz@infradead.org, acme@redhat.com, linux-kernel@vger.kernel.org
Cc: eranian@google.com, ak@linux.intel.com, namhyung@kernel.org,
irogers@google.com, Kan Liang <kan.liang@linux.intel.com>
Subject: [PATCH 2/2] perf docs: Update the documentation for the save_type filter
Date: Tue, 16 Aug 2022 05:56:12 -0700 [thread overview]
Message-ID: <20220816125612.2042397-2-kan.liang@linux.intel.com> (raw)
In-Reply-To: <20220816125612.2042397-1-kan.liang@linux.intel.com>
From: Kan Liang <kan.liang@linux.intel.com>
Update the documentation to reflect the kernel changes.
Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
---
tools/perf/Documentation/perf-record.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tools/perf/Documentation/perf-record.txt b/tools/perf/Documentation/perf-record.txt
index 099817ef5150..d5c57ac1ee0a 100644
--- a/tools/perf/Documentation/perf-record.txt
+++ b/tools/perf/Documentation/perf-record.txt
@@ -397,6 +397,9 @@ following filters are defined:
- abort_tx: only when the target is a hardware transaction abort
- cond: conditional branches
- save_type: save branch type during sampling in case binary is not available later
+ For the platforms with Intel Arch LBR support (12th-Gen+ client or
+ 4th-Gen Xeon+ server), the save branch type is unconditionally enabled
+ when the taken branch stack sampling is enabled.
+
The option requires at least one branch type among any, any_call, any_ret, ind_call, cond.
--
2.35.1
next prev parent reply other threads:[~2022-08-16 12:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 12:56 [PATCH 1/2] perf/x86/lbr: Enable the branch type for the Arch LBR by default kan.liang
2022-08-16 12:56 ` kan.liang [this message]
2022-08-25 13:23 ` [PATCH 2/2] perf docs: Update the documentation for the save_type filter Liang, Kan
2022-08-22 9:00 ` [tip: perf/urgent] perf/x86/lbr: Enable the branch type for the Arch LBR by default tip-bot2 for Kan Liang
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=20220816125612.2042397-2-kan.liang@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox