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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 7 Apr 2009 07:37:39 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	David Woodhouse <dwmw2@...radead.org>
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)


* David Woodhouse <dwmw2@...radead.org> wrote:

> Linus, please pull from
> 	git://git.infradead.org/iommu-2.6.git
> 
> It adds support for suspend/resume, allows us to use interrupt remapping
> without x2apic, and fixes the device-to-iommu mapping for devices behind
> PCI-PCI bridges.
> 
> It also fixes device-to-iommu mapping in the case where we have
> overlapping bus numbers on different PCI domains. Not that that ever
> really happens on x86, but it offended me.
> 
> The bits touching APIC code were Acked-By: Ingo.
> 
> David Woodhouse (3):
>       intel-iommu: Add for_each_iommu() and for_each_active_iommu() macros
>       intel-iommu: Fix device-to-iommu mapping for PCI-PCI bridges.
>       intel-iommu: Handle PCI domains appropriately.
> 
> Fenghua Yu (3):
>       Intel IOMMU Suspend/Resume Support - DMAR
>       Intel IOMMU Suspend/Resume Support - Queued Invalidation
>       Intel IOMMU Suspend/Resume Support - Interrupt Remapping
> 
> Han, Weidong (3):
>       intel-iommu: set compatibility format interrupt
>       x86, dmar: check if it's initialized before disable queue invalidation
>       x2apic/intr-remap: decouple interrupt remapping from x2apic
> 
>  arch/x86/Kconfig               |    2 +-
>  arch/x86/include/asm/apic.h    |    3 +
>  arch/x86/include/asm/io_apic.h |   11 +-
>  arch/x86/kernel/apic/apic.c    |   70 +++++++++++--
>  arch/x86/kernel/apic/io_apic.c |  140 ++++++++++++++++--------
>  drivers/pci/dmar.c             |   71 ++++++++++---
>  drivers/pci/intel-iommu.c      |  238 +++++++++++++++++++++++++++++++++++-----
>  drivers/pci/intr_remapping.c   |   83 ++++++++++++++-
>  include/linux/dmar.h           |   11 ++
>  include/linux/intel-iommu.h    |   13 ++
>  10 files changed, 537 insertions(+), 105 deletions(-)

I suspect these bits are the ones that broke the upstream build:

 drivers/pci/dmar.c:47: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘dmar_tbl_size’
 drivers/pci/dmar.c:62: warning: ‘struct acpi_dmar_device_scope’ declared inside parameter list
 drivers/pci/dmar.c:62: warning: its scope is only this definition or declaration, which is probably not what you want

config attached.

	Ingo

View attachment "config" of type "text/plain" (68250 bytes)