linux-kernel - Re: x86 status was Re: -mm merge plans for 2.6.23

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: <1184191488.12353.160.camel@chaos>
Date:	Thu, 12 Jul 2007 00:04:48 +0200
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Ingo Molnar <mingo@...e.hu>, Andi Kleen <andi@...stfloor.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	Arjan van de Ven <arjan@...radead.org>,
	Chris Wright <chrisw@...s-sol.org>
Subject: Re: x86 status was Re: -mm merge plans for 2.6.23

Linus,

On Wed, 2007-07-11 at 14:42 -0700, Linus Torvalds wrote: 
> Here's a big clue: it doesn't matter one _whit_ how much face-slapping you 
> get, or how much effort some programmers have put into the code. It's 
> untested. And no, we are *not* going to do another "rip everything out, 
> and replace it with new code" again.
> 
> Over my dead body.
>
> We're going to do this thing gradually, or not at all.

Can you please shed some light on me, how exactly you switch an
architecture gradually to clock events.

You simply can not convert PIT today and the HPET next week followed by
the local APIC in three month. 

At least not to my knowledge.

> And if somebody feels slighted by the face-slap, and thinks he has already 
> done enough, and isn't interested in doing it gradually, then good 
> riddance. The "not at all" seems like a good idea, and maybe we can 
> re-visit this in a year or two.

I have no problem to brew this for some more time. I got not repulsed by
the 2.6.20 decision, but I have no clue how to communicate with a black
hole.

	tglx


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