linux-kernel - Re: [PATCH 00/14] convert voyager over to the x86 quirks model

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]

Date:	Tue, 14 Apr 2009 20:08:32 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	James Bottomley <James.Bottomley@...senPartnership.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...ux.intel.com>
Subject: Re: [PATCH 00/14] convert voyager over to the x86 quirks model

* Ingo Molnar <mingo@...e.hu> wrote:

> 
> * James Bottomley <James.Bottomley@...senPartnership.com> wrote:
> 
> >  39 files changed, 554 insertions(+), 726 deletions(-)
> 
> That diffstat is not against current mainline, is it? 
> Would you mind to send a proper diffstat with the revert 
> included as well? That will give us a complete picture.

ok, i did the calculations, and the effect of adding back 
x86/Voyager is roughly:

   48 files changed, 5226 insertions(+), 142 deletions(-)

That's quite a lot, and lets put this into perspective.

You are talking about moving ~5000 lines of legacy code back into 
arch/x86/, for a total of *four* Voyager/Linux systems, which are 
using _ancient_ 486/P5 era CPUs.

Two of these systems are in your house, two are somewhere unknown: 
their owners certainly never sent bugreports against recent mainline 
kernels (Voyager didnt even _build_ for a couple of straight kernel 
releases), and i suspect those boxes are probably decommissioned 
already.

A single core on my run-of-the-mill x86 laptop has more computing 
power than all Voyager/Linux systems on the planet, combined. And 
you now want to add back support to the mainline arch/x86 code, 
which we are trying hard to keep running on millions of x86 Linux 
systems?

You still have not given proper justification for doing that ...

Sorry to be the one to say 'no', but the reasons you gave so far 
were not very convincing to me.

Anyway, you seem to be willing to maintain this code it out of tree. 
If someone owns such an ancient Voyager box and wants to test a new 
kernel then your tree is a good starting point for doing that. 
There's really no pressing need to have this in mainline.

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