linux-kernel - Re: [PATCH 3/9] x86/moorestown: add moorestown platform flags

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: <20090630063513.GJ1351@ucw.cz>
Date:	Tue, 30 Jun 2009 08:35:13 +0200
From:	Pavel Machek <pavel@....cz>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	"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>,
	Jeremy Fitzhardinge <jeremy@...p.org>
Subject: Re: [PATCH 3/9] x86/moorestown: add moorestown platform flags

On Fri 2009-06-26 09:54:54, Jesse Barnes wrote:
> On Fri, 26 Jun 2009 18:32:42 +0200 (CEST)
> Thomas Gleixner <tglx@...utronix.de> wrote:
> 
> > On Fri, 26 Jun 2009, Ingo Molnar wrote:
> > > [ Although it is beyond me why ABP was done - why wasnt HPET good
> > >   enough? HPET can do per CPU clockevents too and it's just as 
> > >   off-chip (and hence fundamentally slow) as ABP. ]
> > 
> > Welcome to the wonderful world of embedded systems. Just have a peek
> > into arch/[arm/powerpc/mips] to see what's coming up to us with full
> > force. I would not be surprised when we see an x86 system sharing the
> > device driver for i2c or whatever with an ARM SoC in the foreseable
> > future.
> 
> Ha, yeah I was just going to say "think embedded".  ABP is a much
> simpler spec and programming interface than HPET, and since we were
> designing new custom silicon, it made sense to just do the simple
> thing, rather than butchering an existing spec, then making a partial
> HPET that looks like ABP anyway and forcing any future HPET updates to
> conform to the new standard (very similar reasoning to the ACPI vs SFI
> discussion btw).  Hopefully the technologies we've come up with for

Very similary wrong, I'd say :-(. While you could have created
hpet-lite, where hpet-lite driver would work on hpet system, you went
and created something new.

And yes, SFI is similar disaster, you should just define subset of
acpi ('acpi-lite').

In the end, you are willing to use silicon for compatibility (arm
 instruction set needs less transistors, right?) and wasting millions
 of transistors, then try to save thousands with non-compatible
 devices :-(.
 
								Pavel
 


-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/