linux-kernel - [RFC PATCH 0/5] amd_iommu: Refactor IOMMU group and support virtual aliases

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:	Mon, 08 Oct 2012 22:49:28 -0600
From:	Alex Williamson <alex.williamson@...hat.com>
To:	Joerg.Roedel@....com, florian@...inger.net
Cc:	iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org
Subject: [RFC PATCH 0/5] amd_iommu: Refactor IOMMU group and support virtual
 aliases

This series is meant to refactor IOMMU group support in amd_iommu
to properly support virtual aliases.  If multiple devices alias to
the same virtual alias, they should be grouped together.  This code
also verifies whether the alias should be the root of the group vs
devices above the alias.

This seems to do the right thing on my system, but that's not saying
a lot since it doesn't do anything interesting with aliases.  I'd
appreciate if Joerg and Florian could test this on their systems.
Thanks,

Alex

---

Alex Williamson (5):
      amd_iommu: Properly account for virtual aliases in IOMMU groups
      amd_iommu: Split IOMMU group allocation and attach
      amd_iommu: Split upstream bus device lookup
      amd_iommu: Split IOMMU Group topology walk
      amd_iommu: Split IOMMU group initialization

 drivers/iommu/amd_iommu.c       |  184 ++++++++++++++++++++++++++++++---------
 drivers/iommu/amd_iommu_types.h |    1 
 2 files changed, 142 insertions(+), 43 deletions(-)
--
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/