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:	Fri, 06 Oct 2006 18:19:57 +0200
From:	Arjan van de Ven <arjan@...radead.org>
To:	Linus Torvalds <torvalds@...l.org>
Cc:	Jeff Garzik <jeff@...zik.org>, Andi Kleen <ak@...e.de>,
	discuss@...-64.org, linux-kernel@...r.kernel.org
Subject: Re: [discuss] Re: Please pull x86-64 bug fixes

On Fri, 2006-10-06 at 09:07 -0700, Linus Torvalds wrote:
> 
> On Fri, 6 Oct 2006, Arjan van de Ven wrote:
> >
> > we can do a tiny bit better than the current code; some chipsets have
> > the address of the MMIO region stored in their config space; so we can
> > get to that using the old method and validate the acpi code with that.
> 
> Yes. I think trusting ACPI is _always_ a mistake. It's insane. We should 
> never ask the firmware for any data that we can just figure out ourselves.
> 
> And we should tell all hardware companies that firmware tables are stupid, 
> and that we just want to know what the hell the registers MEAN!

the chipset docs do tell us that. I can even buy a case of "if we know
the chipset, just exclusively use the address from that ignore acpi".
I'm trying to find out how uniform the register format is across
chipsets, it seems many are the same, but there might be 2 varieties ;(


> 
> I've certainly tried to tell Intel that. I think they may even have heard 
> me occasionally.
> 
> I can't understand why some people _still_ think ACPI is a good idea..

I'm the wrong person to rant about ACPI against ;)


-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com

-
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