Skip to contentSkip to conversation

IOMMU Fixes for Linux v3.16-rc2

GIT PULL Joerg Roedel 2 participants 3 messages Jun 24, 2014 – Jun 30, 2014

lore
Share & tools
lore
#0 lore raw

Hi Linus,

The following changes since commit 7171511eaec5bf23fb06078f59784a3a0626b38f:

Linux 3.16-rc1 (2014-06-15 17:45:28 -1000)

are available in the git repository at:

git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v3.16-rc1

for you to fetch changes up to d73a6d722a675dbba8f6b52c964a7076a24a12c1:

iommu/amd: Fix small race between invalidate_range_end/start (2014-06-20 16:14:22 +0200)

----------------------------------------------------------------
IOMMU Fixes for Linux v3.16-rc1

* Fix VT-d regression with handling multiple RMRR entries per device
* Fix a small race that was left in the mmu_notifier handling in the AMD IOMMUv2 driver

----------------------------------------------------------------
Jiang Liu (1):
iommu/vt-d: fix bug in handling multiple RMRRs for the same PCI device

Joerg Roedel (1):
iommu/amd: Fix small race between invalidate_range_end/start

 drivers/iommu/amd_iommu_v2.c | 18 +++++++++++++-----
 drivers/iommu/intel-iommu.c  |  9 +++------
 2 files changed, 16 insertions(+), 11 deletions(-)

Please pull.

Thanks,

Joerg

#1 lore raw

Joerg,
this email was in my spam-box. No real indication as to why, although
the usual suspect is

Received-SPF: none (google.com: [email protected] does not designate
permitted sender hosts) client-ip=85.214.48.195;

presumably together with some other trigger that makes gmail unhappy.

Anyway, pulled,

Linus

Quoted 9 lines · Joerg Roedel

git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v3.16-rc1

IOMMU Fixes for Linux v3.16-rc1

* Fix VT-d regression with handling multiple RMRR entries per device
* Fix a small race that was left in the mmu_notifier handling in the AMD IOMMUv2 driver

#2 lore raw

Hi Linus,

Quoted 5 lines · Linus Torvalds

this email was in my spam-box. No real indication as to why, although
the usual suspect is

Received-SPF: none (google.com: [email protected] does not designate
permitted sender hosts) client-ip=85.214.48.195;

Hmm, I tried to enable SPF for 8bytes.org on the weekend. Unfortunatly my server provider only allows me to edit DNS via some GUI which has no SPF switch... Anyway, I'll try to find a solution for that.

Quoted 3 lines

presumably together with some other trigger that makes gmail unhappy.

Anyway, pulled,

Thanks!

Joerg