linux-kernel - [PATCH][RT 4.1] sched/rt: Have the schedule IPI irq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20150617155225.0fa2f6f4@gandalf.local.home>
Date:	Wed, 17 Jun 2015 15:52:25 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-rt-users <linux-rt-users@...r.kernel.org>,
	Peter Zijlstra <peterz@...radead.org>
Subject: [PATCH][RT 4.1] sched/rt: Have the schedule IPI irq_work run in
 hard irq context


[ Sebastian, you'll need this for porting to 4.1 ]

As the sched rt pull work has moved to using irq_work IPI, having it
delayed to threading pretty much defeats the purpose. The handle also
expects interrupts to be disabled when called as it takes the rq locks.

Set the rt push ipi irq_work handle flag HARD_IRQ

Signed-off-by: Steven Rostedt <rostedt@...dmis.org>
---
 kernel/sched/rt.c |    1 +
 1 file changed, 1 insertion(+)

Index: linux-test.git/kernel/sched/rt.c
===================================================================
--- linux-test.git.orig/kernel/sched/rt.c	2015-06-17 09:30:02.430137824 -0400
+++ linux-test.git/kernel/sched/rt.c	2015-06-17 15:30:57.543881386 -0400
@@ -90,6 +90,7 @@ void init_rt_rq(struct rt_rq *rt_rq)
 	rt_rq->push_cpu = nr_cpu_ids;
 	raw_spin_lock_init(&rt_rq->push_lock);
 	init_irq_work(&rt_rq->push_work, push_irq_work_func);
+	rt_rq->push_work.flags |= IRQ_WORK_HARD_IRQ;
 #endif
 #endif /* CONFIG_SMP */
 	/* We start is dequeued state, because no RT tasks are queued */
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/