From: Ingo Molnar <mingo@kernel.org>
To: Maksim Davydov <davydov-max@yandex-team.ru>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
gpiccoli@igalia.com, den-plotnikov@yandex-team.ru,
dave.hansen@linux.intel.com, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de
Subject: Re: [PATCH] x86/split_lock: fix delayed detection enabling
Date: Thu, 21 Mar 2024 21:11:41 +0100 [thread overview]
Message-ID: <ZfyUfTI4vjmeu8Kv@gmail.com> (raw)
In-Reply-To: <20240321195522.24830-1-davydov-max@yandex-team.ru>
* Maksim Davydov <davydov-max@yandex-team.ru> wrote:
> If the warn mode with disabled mitigation mode is used, then on each cpu
> where the split lock occurred detection will be disabled in order to make
> progress and delayed work will be scheduled, which then will enable
> detection back. Now it turns out that all CPUs use one global delayed
> work structure. This leads to the fact that if a split lock occurs on
> several CPUs at the same time (within 2 jiffies), only one cpu will
> schedule delayed work, but the rest will not. The return value of
> schedule_delayed_work_on() would have shown this, but it is not checked
> in the code
> In order to fix the warn mode with disabled mitigation mode, delayed work
> has to be a per-cpu.
Please be more careful about changelog typography. The above portion has:
- ~3 capitalization inconsistencies
- one missing period
> +/*
> + * In order for each cpu to schedule itself delayed work independently of the
> + * others, delayed work struct should be per-cpu. This is not required when
> + * sysctl_sld_mitigate is enabled because of the semaphore that limits
> + * the number of simultaneously scheduled delayed works to 1.
> + */
... and some of that seeped into this comment block as well, plus there's a
missing comma as well.
Thanks,
Ingo
next prev parent reply other threads:[~2024-03-21 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 19:55 [PATCH] x86/split_lock: fix delayed detection enabling Maksim Davydov
2024-03-21 20:11 ` Ingo Molnar [this message]
2024-03-31 17:07 ` Guilherme G. Piccoli
2024-04-19 10:15 ` Maksim Davydov
2024-04-19 11:26 ` Maksim Davydov
2024-04-21 18:27 ` Guilherme G. Piccoli
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=ZfyUfTI4vjmeu8Kv@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=davydov-max@yandex-team.ru \
--cc=den-plotnikov@yandex-team.ru \
--cc=gpiccoli@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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