public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: [patch V4 0/2] smp: Make softirq handling RT friendly
Date: Tue, 12 Apr 2022 22:51:45 +0200 (CEST)	[thread overview]
Message-ID: <20220412203649.956258017@linutronix.de> (raw)

The invocation of do_softirq() in flush_smp_call_function_from_idle()
breaks on RT because RT does not provide do_softirq().

Aside of that flush_smp_call_function_from_idle() is a misnomer since the
function is invoked not only from idle, but also from the scheduler
migration thread.

The following series addresses this. Changes vs. V3, which can be found
here: https://lore.kernel.org/lkml/YgKgL6aPj8aBES6G@linutronix.de

  - Rename flush_smp_call_function_from_idle() and add comments

  - Confine the RT specifics in the softirq code

Thanks,

	tglx
---
 include/linux/interrupt.h |    9 +++++++++
 kernel/sched/core.c       |    2 +-
 kernel/sched/idle.c       |    2 +-
 kernel/sched/sched.h      |    4 ++--
 kernel/smp.c              |   32 ++++++++++++++++++++++++--------
 kernel/softirq.c          |   13 +++++++++++++
 6 files changed, 50 insertions(+), 12 deletions(-)





             reply	other threads:[~2022-04-12 20:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 20:51 Thomas Gleixner [this message]
2022-04-12 20:51 ` [patch V4 1/2] smp: Rename flush_smp_call_function_from_idle() Thomas Gleixner
2022-04-13  2:52   ` kernel test robot
2022-04-13 13:00     ` Thomas Gleixner
2022-04-13  2:53   ` kernel test robot
2022-04-12 20:51 ` [patch V4 2/2] smp: Make softirq handling RT safe in flush_smp_call_function_queue() Thomas Gleixner

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=20220412203649.956258017@linutronix.de \
    --to=tglx@linutronix.de \
    --cc=bigeasy@linutronix.de \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.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