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: <20080901161639.5215db63@infradead.org>
Date:	Mon, 1 Sep 2008 16:16:39 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	David Woodhouse <dwmw2@...radead.org>,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: Misc fixes for 2.6.27

On Tue, 02 Sep 2008 01:01:19 +0200
Andi Kleen <andi@...stfloor.org> wrote:

> Arjan van de Ven <arjan@...radead.org> writes:
> 
> > On Tue, 02 Sep 2008 00:32:16 +0200
> > Andi Kleen <andi@...stfloor.org> wrote:
> >
> >> David Woodhouse <dwmw2@...radead.org> writes:
> >> > +
> >> > +static struct dmi_system_id __initdata intel_iommu_dmi_table[]
> >> > = {
> >> > +	{	/* Some DG33BU BIOS revisions advertised
> >> > non-existent VT-d */
> >> 
> >> Are you sure it's non existent? A G33 chipset should have it in
> >> hardware I thought.
> >
> > nope they don't/
> > later ones and some other models do though, but not the G33
> 
> I see. But presumably that chipset will be in other motherboards
> too and that BIOS bug might be also wider spread. So it would be
> still better to key off an PCI-ID or similar.
> 

it would be nice, no doubt, unfortunately this code runs (and needs to
run) before the PCI subsystem is initialized...

-- 
If you want to reach me at my work email, use arjan@...ux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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