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: <20090626125111.GA11575@elte.hu>
Date:	Fri, 26 Jun 2009 14:51:11 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	"Pan, Jacob jun" <jacob.jun.pan@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...ux.intel.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 3/9] x86/moorestown: add moorestown platform flags


* Alan Cox <alan@...rguk.ukuu.org.uk> wrote:

> > That's a pretty bogus claim - on x86 a bootloader generally 
> > knows very little about 'what it is running on'. We do most of 
> > the enumeration in early platform code and retrieve information 
> > via standard BIOS interfaces.
> 
> Stop thinking about existing x86 PC systems running grub for a 
> bit. [...]

You are talking to the wrong person then i guess, i'm not going to 
ignore 95% of our installed base. ;-)

We will gladly take clean x86 patches that abstract away lowlevel 
details of x86 platforms, and have been taking them and have been 
writing them for a long time. If this patch-set can shape itself in 
such a way (as i requested), without hindering the common case, it 
is certainly welcome.

Generally, if you try to deviate from de facto standards then you 
better show a very good reason and much cleaner code than this 
deficient v1 patch-set.

Yes, platform abstraction is good if it's necessary and if it's done 
cleanly, and x86 certainly has a few things to learn in that area 
(it still has way too much platform spaghetti), but i'm not 
convinced here at all that it's necessary, and it's certainly not 
cleanly done at all. As i pointed it out in my review in detail, 
it's full of 'if (feature)' crap invading core platform code for 
example.

There's good examples as well, from the same quarters of Intel: for 
example i reviewed and commented on the related SFI patches a few 
days ago, and they looked distinctly clean and desirable.

Thanks,

	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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ