From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: [GIT PULL] dma-mapping updates for Linux 5.17
Date: Mon, 10 Jan 2022 19:46:02 +0100 [thread overview]
Message-ID: <Ydx+6rmjq2giOC/b@infradead.org> (raw)
The following changes since commit 0fcfb00b28c0b7884635dacf38e46d60bf3d4eb1:
Linux 5.16-rc4 (2021-12-05 14:08:22 -0800)
are available in the Git repository at:
git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-5.17
for you to fetch changes up to f857acfc457ea63fa5b862d77f055665d863acfe:
lib/scatterlist: cleanup macros into static inline functions (2021-12-22 09:21:43 +0100)
----------------------------------------------------------------
dma-mapping updates for Linux 5.17
- refactor the dma-direct coherent allocator
- turn an macro into an inline in scatterlist.h (Logan Gunthorpe)
----------------------------------------------------------------
Christoph Hellwig (11):
dma-direct: factor out dma_set_{de,en}crypted helpers
dma-direct: don't call dma_set_decrypted for remapped allocations
dma-direct: always leak memory that can't be re-encrypted
dma-direct: clean up the remapping checks in dma_direct_alloc
dma-direct: factor out a helper for DMA_ATTR_NO_KERNEL_MAPPING allocations
dma-direct: refactor the !coherent checks in dma_direct_alloc
dma-direct: fail allocations that can't be made coherent
dma-direct: warn if there is no pool for force unencrypted allocations
dma-direct: drop two CONFIG_DMA_RESTRICTED_POOL conditionals
dma-direct: factor the swiotlb code out of __dma_direct_alloc_pages
dma-direct: add a dma_direct_use_pool helper
Logan Gunthorpe (1):
lib/scatterlist: cleanup macros into static inline functions
include/linux/scatterlist.h | 29 ++++--
kernel/dma/direct.c | 240 ++++++++++++++++++++++++++------------------
2 files changed, 163 insertions(+), 106 deletions(-)
next reply other threads:[~2022-01-10 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 18:46 Christoph Hellwig [this message]
2022-01-12 19:12 ` 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=Ydx+6rmjq2giOC/b@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
all inboxes | Powered by JetHome®