From: patchwork-bot+linux-riscv@kernel.org
To: Eric Lin <eric.lin@sifive.com>
Cc: linux-riscv@lists.infradead.org, atishp@atishpatra.org,
anup@brainfault.org, will@kernel.org, mark.rutland@arm.com,
palmer@dabbelt.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, greentime.hu@sifive.com,
vincent.chen@sifive.com
Subject: Re: [PATCH] perf: RISC-V: Remove PERF_HES_STOPPED flag checking in riscv_pmu_start()
Date: Wed, 12 Jul 2023 16:00:21 +0000 [thread overview]
Message-ID: <168917762163.26837.1392502139104305103.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230710154328.19574-1-eric.lin@sifive.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Mon, 10 Jul 2023 15:43:28 +0000 you wrote:
> Since commit 096b52fd2bb4 ("perf: RISC-V: throttle perf events") the
> perf_sample_event_took() function was added to report time spent in
> overflow interrupts. If the interrupt takes too long, the perf framework
> will lower the sysctl_perf_event_sample_rate and max_samples_per_tick.
> When hwc->interrupts is larger than max_samples_per_tick, the
> hwc->interrupts will be set to MAX_INTERRUPTS, and events will be
> throttled within the __perf_event_account_interrupt() function.
>
> [...]
Here is the summary with links:
- perf: RISC-V: Remove PERF_HES_STOPPED flag checking in riscv_pmu_start()
https://git.kernel.org/riscv/c/66843b14fb71
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:[~2023-07-12 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 15:43 [PATCH] perf: RISC-V: Remove PERF_HES_STOPPED flag checking in riscv_pmu_start() Eric Lin
2023-07-12 15:52 ` Palmer Dabbelt
2023-07-12 16: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=168917762163.26837.1392502139104305103.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=anup@brainfault.org \
--cc=atishp@atishpatra.org \
--cc=eric.lin@sifive.com \
--cc=greentime.hu@sifive.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=vincent.chen@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