From: Joerg Roedel <joro@8bytes.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: [git pull] IOMMU Fixes for Linux v5.5-rc2
Date: Fri, 20 Dec 2019 12:30:26 +0100 [thread overview]
Message-ID: <20191220113020.GA18747@8bytes.org> (raw)
Hi Linus,
thanks for taking care of the KASAN related IOMMU fix while I was dived
into other development work and sorry for the inconvenience. Here are
the other IOMMU fixes that piled up during the last weeks:
The following changes since commit d1eef1c619749b2a57e514a3fa67d9a516ffa919:
Linux 5.5-rc2 (2019-12-15 15:16:08 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v5.5-rc2
for you to fetch changes up to c18647900ec864d401ba09b3bbd5b34f331f8d26:
iommu/dma: Relax locking in iommu_dma_prepare_msi() (2019-12-18 17:41:36 +0100)
----------------------------------------------------------------
IOMMU Fixes for Linux v5.5-rc2
Including:
- Fix kmemleak warning in IOVA code
- Fix compile warnings on ARM32/64 in dma-iommu code due to
dma_mask type mismatches
- Make ISA reserved regions relaxable, so that VFIO can assign
devices which have such regions defined
- Fix mapping errors resulting in IO page-faults in the VT-d
driver
- Make sure direct mappings for a domain are created after the
default domain is updated
- Map ISA reserved regions in the VT-d driver with correct
permissions
- Remove unneeded check for PSI capability in the IOTLB flush
code of the VT-d driver
- Lockdep fix iommu_dma_prepare_msi()
----------------------------------------------------------------
Alex Williamson (1):
iommu/vt-d: Set ISA bridge reserved region as relaxable
Jerry Snitselaar (2):
iommu: set group default domain before creating direct mappings
iommu/vt-d: Allocate reserved region for ISA with correct permission
Lu Baolu (2):
iommu/vt-d: Fix dmar pte read access not set error
iommu/vt-d: Remove incorrect PSI capability check
Robin Murphy (2):
iommu/dma: Rationalise types for DMA masks
iommu/dma: Relax locking in iommu_dma_prepare_msi()
Xiaotao Yin (1):
iommu/iova: Init the struct iova to fix the possible memleak
drivers/iommu/dma-iommu.c | 23 +++++++++++------------
drivers/iommu/intel-iommu.c | 12 ++----------
drivers/iommu/intel-svm.c | 6 +-----
drivers/iommu/iommu.c | 4 ++--
drivers/iommu/iova.c | 2 +-
5 files changed, 17 insertions(+), 30 deletions(-)
Please pull.
Thanks,
Joerg
next reply other threads:[~2019-12-20 11:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 11:30 Joerg Roedel [this message]
2019-12-20 18:45 ` [git pull] IOMMU Fixes for Linux v5.5-rc2 pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191220113020.GA18747@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox