linux-kernel - Dynamically determine if kernel includes CFS Scheduler

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 for Android: free password hash cracker in your pocket

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

Message-ID: <49B18B2E.606@us.ibm.com>
Date:	Fri, 06 Mar 2009 12:44:30 -0800
From:	Darren Hart <dvhltc@...ibm.com>
To:	Peter Zijlstra <peterz@...radead.org>
CC:	Ingo Molnar <mingo@...e.hu>,
	"lkml, " <linux-kernel@...r.kernel.org>
Subject: Dynamically determine if kernel includes CFS Scheduler

I've received an internal request for a means to determine at run-time 
if the CFS scheduler is included in the running kernel.  Looking through 
the git commit log and the /proc/sys/kernel filesystem, I think I see 
two approaches:

1) stat("/proc/sys/kernel/sched_compat_yield")
    This confirms 2.6.23-rc7 kernel or later which definitely has the CFS
    scheduler and this functionality is of interest anyway.
2) Test if the kernel version is >= 2.6.22 which is where I believe CFS
    landed.

Any guesses as to how robust/future-proof approach #1 would be?

-- 
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team
--
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/