linux-kernel - Re: BUG in drivers/dma/ioat/dma

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:	Wed, 30 Jun 2010 21:02:05 +0100
From:	David Woodhouse <David.Woodhouse@...el.com>
To:	"Williams, Dan J" <dan.j.williams@...el.com>
Cc:	Chris Li <lkml@...isli.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: BUG in drivers/dma/ioat/dma_v2.c:314

On Wed, 2010-06-30 at 20:40 +0100, Williams, Dan J wrote:
>  From the dmesg:
> > IOMMU 0: reg_base_addr fe710000 ver 1:0 cap 900000c2f0462 ecap e01
> > DMAR: DRHD base: 0x000000fe714000 flags: 0x0
> > IOMMU 1: reg_base_addr fe714000 ver 1:0 cap 900000c2f0462 ecap e01
> > DMAR: DRHD base: 0x000000fe719000 flags: 0x0
> > IOMMU 2: reg_base_addr fe719000 ver 1:0 cap 900000c2f0462 ecap e01
> > DMAR: DRHD base: 0x000000fe718000 flags: 0x1
> > IOMMU 3: reg_base_addr fe718000 ver 1:0 cap 900000c2f0462 ecap e01
> 
> Where we expect bit 54 to be set for the DMA iommu, and it does not 
> appear to show up.

So the BIOS is lying to us about which PCI devices are attached to which
IOMMU?

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@...el.com                              Intel Corporation

--
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/