From: Oleksii Kurochko <oleksii.kurochko@gmail.com>
To: Jan Beulich <jbeulich@suse.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH for-4.21 00/10] x86/HPET: broadcast IRQ and other improvements
Date: Fri, 17 Oct 2025 18:03:52 +0200 [thread overview]
Message-ID: <514f41ba-e901-459c-b2e5-9db2e509c933@gmail.com> (raw)
In-Reply-To: <8d94abf8-70d1-478c-885e-ff9a960ac72d@suse.com>
[-- Attachment #1: Type: text/plain, Size: 2038 bytes --]
On 10/16/25 9:30 AM, Jan Beulich wrote:
> While 1db7829e5657 ("x86/hpet: do local APIC EOI after interrupt processing")
> helped quite a bit, nested interrupts could still occur. First and foremost
> as a result from IRQ migration (where we don't have any control over the
> vectors chosen). Hence besides reducing the number of IRQs that can be raised
> (first two patches) and possibly the number of invocations of
> handle_hpet_broadcast() from the IRQ handler (optional patch 4), the main
> goal here is to eliminate the potential for nested IRQs (patch 3). These
> patches are imo 4.21 candidates (with patch 4 being questionable altogether;
> see there).
I am not sure that patch 4 is very useful at the current stage.
The first three patches look useful enough for now, so:
Releaase-Acked-by: Oleksii Kurochko<oleksii.kurochko@gmail.com>
~ Oleksii
> Patches 5 and onwards likely aren't important enough anymore at
> this point of the release cycle, even if those with a Fixes: tag would likely
> end up being backported later on.
>
> The one related thing I haven't been able to find a viable solution for is
> the elimination of the cpumask_t local variable in handle_hpet_broadcast().
> That'll get in the way of possible future increases of the NR_CPUS upper
> bound: Much like right now a single level of nesting is already too much,
> if the limit was doubled even a single IRQ would end up consuming too much
> stack space (together with cpumask_raise_softirq() also having such a
> variable). Yet further doubling would not allow any such stack variables
> anymore.
>
> 01: limit channel changes
> 02: disable unused channels
> 03: use single, global, low-priority vector for broadcast IRQ
> 04: ignore "stale" IRQs
> 05: avoid indirect call to event handler
> 06: make another channel flags update atomic
> 07: move legacy tick IRQ count adjustment
> 08: shrink IRQ-descriptor locked region in set_channel_irq_affinity()
> 09: reduce hpet_next_event() call sites
> 10: don't use hardcoded 0 for "long timeout"
>
> Jan
[-- Attachment #2: Type: text/html, Size: 2598 bytes --]
prev parent reply other threads:[~2025-10-17 16:04 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 7:30 [PATCH for-4.21 00/10] x86/HPET: broadcast IRQ and other improvements Jan Beulich
2025-10-16 7:31 ` [PATCH for-4.21 01/10] x86/HPET: limit channel changes Jan Beulich
2025-10-16 10:24 ` Roger Pau Monné
2025-10-16 11:47 ` Jan Beulich
2025-10-16 15:07 ` Roger Pau Monné
2025-10-16 15:16 ` Jan Beulich
2025-10-16 15:25 ` Roger Pau Monné
2025-10-17 9:23 ` Roger Pau Monné
2025-10-17 9:55 ` Jan Beulich
2025-10-16 7:31 ` [PATCH for-4.21 02/10] x86/HPET: disable unused channels Jan Beulich
2025-10-16 11:42 ` Roger Pau Monné
2025-10-16 11:57 ` Jan Beulich
2025-10-16 15:34 ` Roger Pau Monné
2025-10-16 15:55 ` Jan Beulich
2025-10-16 16:28 ` Roger Pau Monné
2025-10-16 16:31 ` Roger Pau Monné
2025-10-17 6:08 ` Jan Beulich
2025-10-17 6:10 ` Jan Beulich
2025-10-16 7:32 ` [PATCH for-4.21 03/10] x86/HPET: use single, global, low-priority vector for broadcast IRQ Jan Beulich
2025-10-16 16:27 ` Roger Pau Monné
2025-10-17 7:15 ` Jan Beulich
2025-10-17 8:20 ` Roger Pau Monné
2025-10-20 5:53 ` Jan Beulich
2025-10-20 15:49 ` Roger Pau Monné
2025-10-20 16:05 ` Jan Beulich
2025-10-21 8:37 ` Roger Pau Monné
2025-10-16 17:01 ` Andrew Cooper
2025-10-17 6:23 ` Jan Beulich
2025-10-16 7:32 ` [PATCH for-4.21 04/10] x86/HPET: ignore "stale" IRQs Jan Beulich
2025-10-17 9:19 ` Roger Pau Monné
2025-10-17 9:57 ` Jan Beulich
2025-10-17 12:13 ` Roger Pau Monné
2025-10-16 7:32 ` [PATCH 05/10] x86/HPET: avoid indirect call to event handler Jan Beulich
2025-10-16 7:33 ` [PATCH 06/10] x86/HPET: make another channel flags update atomic Jan Beulich
2025-10-16 7:33 ` [PATCH 07/10] x86/HPET: move legacy tick IRQ count adjustment Jan Beulich
2025-10-16 7:34 ` [PATCH 08/10] x86/HPET: shrink IRQ-descriptor locked region in set_channel_irq_affinity() Jan Beulich
2025-10-16 7:34 ` [PATCH 09/10] x86/HPET: reduce hpet_next_event() call sites Jan Beulich
2025-10-16 7:35 ` [PATCH 10/10] x86/HPET: don't use hardcoded 0 for "long timeout" Jan Beulich
2025-10-16 10:05 ` [PATCH for-4.21 00/10] x86/HPET: broadcast IRQ and other improvements Roger Pau Monné
2025-10-16 10:41 ` Jan Beulich
2025-10-17 16:03 ` Oleksii Kurochko [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=514f41ba-e901-459c-b2e5-9db2e509c933@gmail.com \
--to=oleksii.kurochko@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.