All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <frederic@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Frederic Weisbecker <frederic@kernel.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Marco Crivellari <marco.crivellari@suse.com>,
	Waiman Long <llong@redhat.com>,
	cgroups@vger.kernel.org
Subject: [PATCH 0/3 v3] genirq: Fix IRQ threads VS cpuset
Date: Fri, 21 Nov 2025 15:34:57 +0100	[thread overview]
Message-ID: <20251121143500.42111-1-frederic@kernel.org> (raw)

Hi,

Here is another take after some last minutes issues reported by
Marek Szyprowski <m.szyprowski@samsung.com>:

https://lore.kernel.org/all/73356b5f-ab5c-4e9e-b57f-b80981c35998@samsung.com/


Changes since v2:

* Fix early spurious IRQ thread wake-up (to be SOB'ed by Thomas)

* Instead of applying the affinity remotely, set PF_NO_SETAFFINITY
  early, right after kthread creation, and wait for the thread to
  apply the affinity by itself. This is to prevent from early wake-up
  to mess up with kthread_bind_mask(), as reported by
  Marek Szyprowski <m.szyprowski@samsung.com>

Frederic Weisbecker (2):
  genirq: Fix interrupt threads affinity vs. cpuset isolated partitions
  genirq: Remove cpumask availability check on kthread affinity setting

Thomas Gleixner (1):
  genirq: Prevent from early irq thread spurious wake-ups

 kernel/irq/handle.c | 10 +++++++++-
 kernel/irq/manage.c | 40 +++++++++++++++++++---------------------
 2 files changed, 28 insertions(+), 22 deletions(-)

-- 
2.51.1


             reply	other threads:[~2025-11-21 14:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20251121143513eucas1p15c03a2c15aa5a0a15cc46d8f0a4e534e@eucas1p1.samsung.com>
2025-11-21 14:34 ` Frederic Weisbecker [this message]
2025-11-21 14:34   ` [PATCH 1/3 v3] genirq: Prevent from early irq thread spurious wake-ups Frederic Weisbecker
2025-11-21 19:12     ` Thomas Gleixner
2025-11-21 22:04       ` Frederic Weisbecker
2025-11-21 20:01     ` [tip: irq/core] genirq: Prevent early spurious wake-ups of interrupt threads tip-bot2 for Thomas Gleixner
2025-11-22  8:30     ` tip-bot2 for Frederic Weisbecker
2025-11-21 14:34   ` [PATCH 2/3 v3] genirq: Fix interrupt threads affinity vs. cpuset isolated partitions Frederic Weisbecker
2025-11-21 16:29     ` Waiman Long
2025-11-21 20:01     ` [tip: irq/core] " tip-bot2 for Frederic Weisbecker
2025-11-22  8:30     ` tip-bot2 for Frederic Weisbecker
2025-12-12  1:48     ` [PATCH 2/3 v3] " Chris Mason
2025-12-12  2:26       ` Thomas Gleixner
2025-12-12  4:01         ` [PATCH] genirq: Don't overwrite interrupt thread flags on setup Thomas Gleixner
2025-12-12 11:57           ` Frederic Weisbecker
2025-12-13  1:37           ` [tip: irq/urgent] " tip-bot2 for Thomas Gleixner
2025-12-18 10:07     ` [PATCH 2/3 v3] genirq: Fix interrupt threads affinity vs. cpuset isolated partitions Guenter Roeck
2025-11-21 14:35   ` [PATCH 3/3 v3] genirq: Remove cpumask availability check on kthread affinity setting Frederic Weisbecker
2025-11-21 20:01     ` [tip: irq/core] " tip-bot2 for Frederic Weisbecker
2025-11-22  8:30     ` tip-bot2 for Frederic Weisbecker
2025-11-21 20:05   ` [PATCH 0/3 v3] genirq: Fix IRQ threads VS cpuset Marek Szyprowski

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=20251121143500.42111-1-frederic@kernel.org \
    --to=frederic@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llong@redhat.com \
    --cc=m.szyprowski@samsung.com \
    --cc=marco.crivellari@suse.com \
    --cc=tglx@linutronix.de \
    /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.