linux-kernel - Re: [GIT *] intel-iommu updates for 2.6.30 (second batch)

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:	Mon, 06 Apr 2009 22:52:34 -0700
From:	David Woodhouse <dwmw2@...radead.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	torvalds@...ux-foundation.org, iommu@...ts.linux-foundation.org,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT *] intel-iommu updates for 2.6.30 (second batch)

On Tue, 2009-04-07 at 07:42 +0200, Ingo Molnar wrote:
> hm, it breaks on all !ACPI configs AFAICS. The whole new code 
> section you added to dmar.c depends on ACPI functionality.
> 
> Restricting DMAR to "depends on ACPI" in the Kconfig would probably 
> work but is somewhat lame: 

Er, DMAR _does_ depend on ACPI:

config DMAR
        bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
        depends on PCI_MSI && ACPI && EXPERIMENTAL

DMAR is the name of an ACPI table. Much of dmar.c is dedicated to
parsing such tables... it was never going to work without ACPI.

> this built fine with !ACPI before and if the hw ever gets discovered
> purely via the PCI space 

That would be lovely... but probably isn't going to happen. Although
that doesn't stop me reminding people how lovely it would be, especially
when BIOS bugs keep screwing us over.

I suspect you have INTR_REMAP without ACPI or DMAR? And INTR_REMAP
should probably depend on ACPI too, unfortunately. As should X2APIC,
therefore.

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