From: patchwork-bot+linux-riscv@kernel.org
To: Pu Lehui <pulehui@huaweicloud.com>
Cc: linux-riscv@lists.infradead.org, bpf@vger.kernel.org,
atishp@atishpatra.org, conor@kernel.org, anup@brainfault.org,
palmer@dabbelt.com, bjorn@kernel.org, pulehui@huawei.com
Subject: Re: [PATCH v2] drivers/perf: riscv: Disable PERF_SAMPLE_BRANCH_* while not supported
Date: Wed, 27 Mar 2024 14:00:29 +0000 [thread overview]
Message-ID: <171154802952.9827.25009069225289323.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240312012053.1178140-1-pulehui@huaweicloud.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Tue, 12 Mar 2024 01:20:53 +0000 you wrote:
> From: Pu Lehui <pulehui@huawei.com>
>
> RISC-V perf driver does not yet support branch sampling. Although the
> specification is in the works [0], it is best to disable such events
> until support is available, otherwise we will get unexpected results.
> Due to this reason, two riscv bpf testcases get_branch_snapshot and
> perf_branches/perf_branches_hw fail.
>
> [...]
Here is the summary with links:
- [v2] drivers/perf: riscv: Disable PERF_SAMPLE_BRANCH_* while not supported
https://git.kernel.org/riscv/c/ea6873118493
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2024-03-27 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 1:20 [PATCH v2] drivers/perf: riscv: Disable PERF_SAMPLE_BRANCH_* while not supported Pu Lehui
2024-03-12 12:52 ` Conor Dooley
2024-03-12 19:12 ` Atish Patra
2024-03-27 14:00 ` patchwork-bot+linux-riscv [this message]
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=171154802952.9827.25009069225289323.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=anup@brainfault.org \
--cc=atishp@atishpatra.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=conor@kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pulehui@huawei.com \
--cc=pulehui@huaweicloud.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