From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] dma-mapping fixes for 5.3
Date: Sat, 20 Jul 2019 19:29:11 +0200 [thread overview]
Message-ID: <20190720172911.GA11099@infradead.org> (raw)
The following changes since commit 9637d517347e80ee2fe1c5d8ce45ba1b88d8b5cd:
Merge tag 'for-linus-20190715' of git://git.kernel.dk/linux-block (2019-07-15 21:20:52 -0700)
are available in the Git repository at:
git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-5.3-1
for you to fetch changes up to 449fa54d6815be8c2c1f68fa9dbbae9384a7c03e:
dma-direct: correct the physical addr in dma_direct_sync_sg_for_cpu/device (2019-07-19 14:09:40 +0200)
----------------------------------------------------------------
dma-mapping fixes for 5.3-rc1
Fix various regressions:
- force unencrypted dma-coherent buffers if encryption bit can't fit
into the dma coherent mask (Tom Lendacky)
- avoid limiting request size if swiotlb is not used (me)
- fix swiotlb handling in dma_direct_sync_sg_for_cpu/device
(Fugang Duan)
----------------------------------------------------------------
Christoph Hellwig (2):
dma-mapping: add a dma_addressing_limited helper
dma-direct: only limit the mapping size if swiotlb could be used
Fugang Duan (1):
dma-direct: correct the physical addr in dma_direct_sync_sg_for_cpu/device
Tom Lendacky (1):
dma-direct: Force unencrypted DMA under SME for certain DMA masks
arch/s390/Kconfig | 1 +
arch/s390/mm/init.c | 7 ++++++-
arch/x86/Kconfig | 1 +
arch/x86/mm/mem_encrypt.c | 30 ++++++++++++++++++++++++++++++
include/linux/dma-direct.h | 9 +++++++++
include/linux/dma-mapping.h | 14 ++++++++++++++
kernel/dma/Kconfig | 3 +++
kernel/dma/direct.c | 44 +++++++++++++++++++-------------------------
8 files changed, 83 insertions(+), 26 deletions(-)
next reply other threads:[~2019-07-20 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-20 17:29 Christoph Hellwig [this message]
2019-07-20 19:35 ` [GIT PULL] dma-mapping fixes for 5.3 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=20190720172911.GA11099@infradead.org \
--to=hch@infradead.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