From: patchwork-bot+linux-riscv@kernel.org
To: Dmitry Shifrin <dmitry.shifrin@syntacore.com>
Cc: linux-riscv@lists.infradead.org, atishp@atishpatra.org,
anup@brainfault.org, will@kernel.org, mark.rutland@arm.com,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, alexghiti@rivosinc.com
Subject: Re: [PATCH] perf: riscv: Fix selecting counters in legacy mode
Date: Thu, 01 Aug 2024 16:40:37 +0000 [thread overview]
Message-ID: <172253043772.13740.4519514649255072983.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240729125858.630653-1-dmitry.shifrin@syntacore.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Mon, 29 Jul 2024 15:58:58 +0300 you wrote:
> It is required to check event type before checking event config.
> Events with the different types can have the same config.
> This check is missed for legacy mode code
>
> For such perf usage:
> sysctl -w kernel.perf_user_access=2
> perf stat -e cycles,L1-dcache-loads --
> driver will try to force both events to CYCLE counter.
>
> [...]
Here is the summary with links:
- perf: riscv: Fix selecting counters in legacy mode
https://git.kernel.org/riscv/c/941a8e9b7a86
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-08-01 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 12:58 [PATCH] perf: riscv: Fix selecting counters in legacy mode Shifrin Dmitry
2024-07-31 7:37 ` Samuel Holland
2024-08-01 8:09 ` Dmitry Shifrin
2024-08-01 16:40 ` 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=172253043772.13740.4519514649255072983.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alexghiti@rivosinc.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@atishpatra.org \
--cc=dmitry.shifrin@syntacore.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox