linux-kernel - [RFC PATCH 1/4] linsched: remove process_all

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: <50442ACA.3000509@linux.vnet.ibm.com>
Date:	Mon, 03 Sep 2012 11:58:02 +0800
From:	Michael Wang <wangyun@...ux.vnet.ibm.com>
To:	LKML <linux-kernel@...r.kernel.org>
CC:	Paul Turner <pjt@...gle.com>,
	Dhaval Giani <dhaval.giani@...il.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: [RFC PATCH 1/4] linsched: remove process_all_softirqs() in main loop
 for accuracy

From: Michael Wang <wangyun@...ux.vnet.ibm.com>

process_all_softirqs() will handle softirq for all the cpu even
it's not the right timing for them, this will cause inaccuracy.

This patch stop invoke process_all_softirqs(), so softirq will
only be handled after timer interrupt arrived.

Signed-off-by: Michael Wang <wangyun@...ux.vnet.ibm.com>
---
 tools/linsched/hrtimer.c |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/tools/linsched/hrtimer.c b/tools/linsched/hrtimer.c
index 26be1d8..de88b25 100644
--- a/tools/linsched/hrtimer.c
+++ b/tools/linsched/hrtimer.c
@@ -206,7 +206,6 @@ void linsched_run_sim(int sim_ticks)
                        /* a handler should never leave this state changed */
                        BUG_ON(smp_processor_id() != active_cpu);

-                       process_all_softirqs();
                        linsched_rcu_invoke();

                        BUG_ON(irqs_disabled());

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