From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: mingo@kernel.org
Cc: linux-kernel@vger.kernel.org, rostedt@goodmis.org,
tglx@linutronix.de, Julia Cartwright <juliac@eso.teric.us>
Subject: [PATCH v3 00/02] Consolidate tasklet + tasklet-hi code
Date: Tue, 27 Feb 2018 17:48:06 +0100 [thread overview]
Message-ID: <20180227164808.10093-1-bigeasy@linutronix.de> (raw)
Ingo made a RT patch a few years back called "tasklet: Prevent tasklets
from going into infinite spin in RT" [0]. I ripped the non-RT pieces out
of it and here they are. I kept him as the original Author.
v1…v3: in v1 I had this_cpu_ptr(&tasklet_hi_vec) without disabling
interrupts and was objected by Steven. There are (indeed) some
users which use this outside if of the interrupt.
So in v2 I moved this but then Julia suggested pass just the
__percpu pointer and use this_cpu_ptr() once interrupts are
disabled.
This is all 1/2. 2/2 is unchanged because tasklet_action() /
tasklet_hi_action() run always in BH and can't migrate to another
CPU between this_cpu_() access and disabling interrupts.
[0] https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git/tree/patches/tasklet-rt-prevent-tasklets-from-going-into-infinite-spin-in-rt.patch?h=linux-4.14.y-rt-patches
Sebastian
next reply other threads:[~2018-02-27 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 16:48 Sebastian Andrzej Siewior [this message]
2018-02-27 16:48 ` [PATCH 1/2] kernel/sofirq: consolidate common code in __tasklet_schedule() + _hi_ Sebastian Andrzej Siewior
2018-03-09 10:54 ` [tip:irq/core] softirq: Consolidate common code in __tasklet_[hi]_schedule() tip-bot for Ingo Molnar
2018-02-27 16:48 ` [PATCH 2/2] kernel/sofirq: consolidate common code in tasklet_action() + tasklet_hi_action() Sebastian Andrzej Siewior
2018-03-09 10:55 ` [tip:irq/core] softirq: Consolidate common code in tasklet_[hi]_action() tip-bot for Ingo Molnar
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=20180227164808.10093-1-bigeasy@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=juliac@eso.teric.us \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).