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, 2 Sep 2008 08:19:20 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Andi Kleen <andi@...stfloor.org>,
	David Woodhouse <dwmw2@...radead.org>,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: Misc fixes for 2.6.27

On Mon, Sep 01, 2008 at 04:16:39PM -0700, Arjan van de Ven wrote:
> 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...

early quirks handles these cases. Check out early-quirks.c

-Andi

-- 
ak@...ux.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