From: Yang Jihong <yangjihong1@huawei.com>
To: <peterz@infradead.org>, <mingo@redhat.com>, <acme@kernel.org>,
<mark.rutland@arm.com>, <alexander.shishkin@linux.intel.com>,
<jolsa@kernel.org>, <namhyung@kernel.org>, <irogers@google.com>,
<eranian@google.com>, <linux-perf-users@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND v3] perf/core: Fix hardlockup failure caused by perf throttle
Date: Fri, 14 Apr 2023 15:04:11 +0800 [thread overview]
Message-ID: <56cc5b4f-3cbd-c265-36fc-fedab16b8cff@huawei.com> (raw)
In-Reply-To: <37d019af-191c-9955-2417-b7cfa5e5efa3@huawei.com>
Hello,
PING again.
Look forward the review.
Thanks,
Yang.
On 2023/3/22 15:36, Yang Jihong wrote:
> Hello,
>
> PING.
>
> This patch has not been responded.
> Please take time to check whether the fix solution is OK.
> Look forward to reviewing the patch. Thanks :)
>
> Thanks,
> Yang.
>
> On 2023/3/6 9:14, Yang Jihong wrote:
>> Hello,
>>
>> PING.
>>
>> Thanks,
>> Yang.
>>
>> On 2023/2/27 10:35, Yang Jihong wrote:
>>> commit e050e3f0a71bf ("perf: Fix broken interrupt rate throttling")
>>> introduces a change in throttling threshold judgment. Before this,
>>> compare hwc->interrupts and max_samples_per_tick, then increase
>>> hwc->interrupts by 1, but this commit reverses order of these two
>>> behaviors, causing the semantics of max_samples_per_tick to change.
>>> In literal sense of "max_samples_per_tick", if hwc->interrupts ==
>>> max_samples_per_tick, it should not be throttled, therefore, the
>>> judgment
>>> condition should be changed to "hwc->interrupts > max_samples_per_tick".
>>>
>>> In fact, this may cause the hardlockup to fail, The minimum value of
>>> max_samples_per_tick may be 1, in this case, the return value of
>>> __perf_event_account_interrupt function is 1.
>>> As a result, nmi_watchdog gets throttled, which would stop PMU (Use x86
>>> architecture as an example, see x86_pmu_handle_irq).
>>>
>>> Fixes: e050e3f0a71b ("perf: Fix broken interrupt rate throttling")
>>> Signed-off-by: Yang Jihong <yangjihong1@huawei.com>
>>> ---
>>>
>>> Changes since v2:
>>> - Add fixed commit.
>>>
>>> Changes since v1:
>>> - Modify commit title.
>>>
>>> kernel/events/core.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/kernel/events/core.c b/kernel/events/core.c
>>> index f79fd8b87f75..0540a8653906 100644
>>> --- a/kernel/events/core.c
>>> +++ b/kernel/events/core.c
>>> @@ -9434,7 +9434,7 @@ __perf_event_account_interrupt(struct
>>> perf_event *event, int throttle)
>>> } else {
>>> hwc->interrupts++;
>>> if (unlikely(throttle
>>> - && hwc->interrupts >= max_samples_per_tick)) {
>>> + && hwc->interrupts > max_samples_per_tick)) {
>>> __this_cpu_inc(perf_throttled_count);
>>> tick_dep_set_cpu(smp_processor_id(),
>>> TICK_DEP_BIT_PERF_EVENTS);
>>> hwc->interrupts = MAX_INTERRUPTS;
>>>
>>
>> .
>
> .
next prev parent reply other threads:[~2023-04-14 7:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 2:35 [PATCH RESEND v3] perf/core: Fix hardlockup failure caused by perf throttle Yang Jihong
2023-03-06 1:14 ` Yang Jihong
2023-03-22 7:36 ` Yang Jihong
2023-04-14 7:04 ` Yang Jihong [this message]
2023-04-14 8:23 ` Peter Zijlstra
2023-04-17 10:46 ` [tip: perf/core] " tip-bot2 for Yang Jihong
2024-08-26 1:27 ` Pengfei Xu
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=56cc5b4f-3cbd-c265-36fc-fedab16b8cff@huawei.com \
--to=yangjihong1@huawei.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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