linux-kernel - Re: [patch] sched_clock(): cleanups, #2

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: <alpine.LFD.0.98.0705250946120.26602@woody.linux-foundation.org>
Date:	Fri, 25 May 2007 09:49:38 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Andi Kleen <andi@...stfloor.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Satyam Sharma <satyam.sharma@...il.com>,
	linux-kernel@...r.kernel.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [patch] sched_clock(): cleanups, #2

On Fri, 25 May 2007, Ingo Molnar wrote:
> 
> ok - then please merge that single hunk into the paravirtops patch - and 
> leave the other 6 hunks in this patch.

Note: I'm actually much more interested in applying the scheduler changes 
than the paravirt-ops changes. It looks like CFS is getting stable, I'd 
much rather have Ingo working on making a nice CFS patch on top of 2.6.22 
(and the current -git tree should obviously approximate that, I don't 
expect any real changes to scheduler stuff), and merge that immediately 
after 2.6.22 is out. 

Ingo: to make things easier, the _best_ split-up would be not "this is the 
historical series of patches leading up to CFS v15" or something like 
that, but it would be nice to get that final CFS version as a series of 
patches that do some specific things rather than as one final one. Is 
there any possibility that could happen? 

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