linux-kernel - [PATCH 0/9] AMD IOMMU: Reduce dependency to struct device

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-next>] [day] [month] [year] [list]

Message-ID: <1307707729-29767-1-git-send-email-joerg.roedel@amd.com>
Date:	Fri, 10 Jun 2011 14:08:40 +0200
From:	Joerg Roedel <joerg.roedel@....com>
To:	<iommu@...ts.linux-foundation.org>, <linux-kernel@...r.kernel.org>
Subject: [PATCH 0/9] AMD IOMMU: Reduce dependency to struct device

Hi,

this patch series reduces the dependency of the AMD IOMMU driver to the
struct device. In fact, it removes the dependency that every request id
the IOMMU can see must have a PCI device in the system. So this is the
real fix for

	https://bugzilla.kernel.org/show_bug.cgi?id=35592

Any (constructive) feedback appreciated!

Regards,

	Joerg

Diffstat:

 arch/x86/include/asm/amd_iommu_types.h |    9 +-
 arch/x86/kernel/amd_iommu.c            |  291 ++++++++++++++++++--------------
 2 files changed, 175 insertions(+), 125 deletions(-)

Shortlog:

Joerg Roedel (9):
      x86/amd-iommu: Remove redundant device_flush_dte() calls
      x86/amd-iommu: Introduce global dev_data_list
      x86/amd-iommu: Store devid in dev_data
      x86/amd-iommu: Store ATS state in dev_data
      x86/amd-iommu: Use only dev_data for dte and iotlb flushing routines
      x86/amd-iommu: Use only dev_data in low-level domain attach/detach functions
      x86/amd-iommu: Allow dev_data->alias to be NULL
      x86/amd-iommu: Search for existind dev_data before allocting a new one
      x86/amd-iommu: Store device alias as dev_data pointer


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