From: Andi Kleen <ak@linux.intel.com>
To: linux-perf-users@vger.kernel.org
Subject: Minor improvements for brstackisn
Date: Fri, 2 Aug 2024 14:14:16 -0700 [thread overview]
Message-ID: <20240802211530.776055-1-ak@linux.intel.com> (raw)
One bug fix and one minor enhancement.
Note one of the patches will likely conflict with Kan's LBR events
patchkit, but the conflict should be easy to resolve (or I will rebase
if that one goes in first)
-Andi
next reply other threads:[~2024-08-02 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 21:14 Andi Kleen [this message]
2024-08-02 21:14 ` [PATCH 1/2] perf script: Add summary to brstackinsn / brstackdisasm Andi Kleen
2024-08-02 21:14 ` [PATCH 2/2] perf report: Handle non capstone case for calling perf script Andi Kleen
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=20240802211530.776055-1-ak@linux.intel.com \
--to=ak@linux.intel.com \
--cc=linux-perf-users@vger.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.