From: Namhyung Kim <namhyung@kernel.org>
To: Leo Yan <leo.yan@arm.com>
Cc: Graham Woodward <graham.woodward@arm.com>,
acme@kernel.org, mark.rutland@arm.com, jolsa@kernel.org,
irogers@google.com, james.clark@linaro.org,
mike.leach@linaro.org, leo.yan@linux.dev,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, nd@arm.com
Subject: Re: [PATCH v1 0/4] perf arm-spe: Allow synthesizing of branch
Date: Tue, 29 Oct 2024 16:09:46 -0700 [thread overview]
Message-ID: <ZyFrOo7K1qmjtaV5@google.com> (raw)
In-Reply-To: <20241029170346.GB24446@e132581.arm.com>
Hi Leo,
On Tue, Oct 29, 2024 at 05:03:46PM +0000, Leo Yan wrote:
> Hi Namhyung,
>
> On Mon, Oct 28, 2024 at 09:40:21AM -0700, Namhyung Kim wrote:
> >
> > Hello,
> >
> > On Fri, Oct 25, 2024 at 03:30:05PM +0100, Graham Woodward wrote:
> > > Currently the --itrace=b will only show branch-misses but this change
> > > allows perf to synthesize branches as well.
> > >
> > > The change also incorporates the ability to display the target
> > > addresses when specifying the addr field if the instruction is a branch.
> > >
> > > Graham Woodward (4):
> > > perf arm-spe: Set sample.addr to target address for instruction sample
> > > perf arm-spe: Use ARM_SPE_OP_BRANCH_ERET when synthesizing branches
> > > perf arm-spe: Correctly set sample flags
> > > perf arm-spe: Update --itrace help text
> >
> > It doesn't apply to perf-tools-next cleanly. Can you please rebase?
>
> I confirmed this series can apply cleanly on the branch [1] with the
> latest commit 150dab31d560 ("perf disasm: Fix not cleaning up
> disasm_line in symbol__disassemble_raw()"):
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git
> branch: perf-tools-next
>
> If you are suggesting for the branch:
>
> [2] https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools.git
> branch: perf-tools
>
> You can see it misses some Arm SPE patches which have been picked up
> in the repo [1].
>
> Please kindly suggest what is right thing to do.
Sorry, my bad. It works ok. I'll add it to tmp.perf-tools-next branch
and run some tests.
Thanks,
Namhyung
next prev parent reply other threads:[~2024-10-29 23:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 14:30 [PATCH v1 0/4] perf arm-spe: Allow synthesizing of branch Graham Woodward
2024-10-25 14:30 ` [PATCH v1 1/4] perf arm-spe: Set sample.addr to target address for instruction sample Graham Woodward
2024-10-25 14:30 ` [PATCH v1 2/4] perf arm-spe: Use ARM_SPE_OP_BRANCH_ERET when synthesizing branches Graham Woodward
2024-10-25 14:30 ` [PATCH v1 3/4] perf arm-spe: Correctly set sample flags Graham Woodward
2024-10-25 14:30 ` [PATCH v1 4/4] perf arm-spe: Update --itrace help text Graham Woodward
2024-10-25 17:33 ` [PATCH v1 0/4] perf arm-spe: Allow synthesizing of branch Leo Yan
2024-10-28 8:34 ` James Clark
2024-10-28 16:40 ` Namhyung Kim
2024-10-29 17:03 ` Leo Yan
2024-10-29 23:09 ` Namhyung Kim [this message]
2024-10-30 9:33 ` Leo Yan
2024-10-30 21:30 ` Namhyung Kim
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=ZyFrOo7K1qmjtaV5@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=graham.woodward@arm.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=leo.yan@arm.com \
--cc=leo.yan@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=nd@arm.com \
/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;
as well as URLs for NNTP newsgroup(s).