linux-kernel - [PATCH 2/5] RT - fix reschedule IPI

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20071009142554.4941.39785.stgit@novell1.haskins.net>
Date:	Tue, 09 Oct 2007 10:25:54 -0400
From:	Gregory Haskins <ghaskins@...ell.com>
To:	mingo@...e.hu, linux-rt-users@...r.kernel.org, rostedt@...dmis.org
Cc:	kravetz@...ibm.com, linux-kernel@...r.kernel.org,
	ghaskins@...ell.com, pmorreale@...ell.com, sdietrich@...ell.com
Subject: [PATCH 2/5] RT - fix reschedule IPI

From: Mike Kravetz <kravetz@...ibm.com>

x86_64 based RESCHED_IPIs fail to set the reschedule flag

Signed-off-by: Steven Rostedt <rostedt@...dmis.org>
Signed-off-by: Gregory Haskins <ghaskins@...ell.com>
---

 arch/x86_64/kernel/smp.c |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/arch/x86_64/kernel/smp.c b/arch/x86_64/kernel/smp.c
index a5bf746..3ce6cad 100644
--- a/arch/x86_64/kernel/smp.c
+++ b/arch/x86_64/kernel/smp.c
@@ -505,13 +505,13 @@ void smp_send_stop(void)
 }
 
 /*
- * Reschedule call back. Nothing to do,
- * all the work is done automatically when
- * we return from the interrupt.
+ * Reschedule call back. Trigger a reschedule pass so that
+ * RT-overload balancing can pass tasks around.
  */
 asmlinkage void smp_reschedule_interrupt(void)
 {
 	ack_APIC_irq();
+	set_tsk_need_resched(current);
 }
 
 asmlinkage void smp_call_function_interrupt(void)

-
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/