From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Subject: [GIT PULL] dma-mapping updates for Linux 6.4
Date: Fri, 28 Apr 2023 08:10:25 +0200 [thread overview]
Message-ID: <ZEtjUWcp6qm4l+zl@infradead.org> (raw)
The following changes since commit 0eee5ae1025699ea93d44fdb6ef2365505082103:
swiotlb: fix slot alignment checks (2023-03-22 09:03:17 +0100)
are available in the Git repository at:
git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-6.4-2023-04-28
for you to fetch changes up to ec274aff21b6a94c7973384ca80a503c1bc3b173:
swiotlb: Omit total_used and used_hiwater if !CONFIG_DEBUG_FS (2023-04-20 14:51:41 +0200)
----------------------------------------------------------------
dma-mapping updates for Linux 6.4
- fix a PageHighMem check in dma-coherent initialization (Doug Berger)
- clean up the coherency defaul initialiation (Jiaxun Yang)
- add cacheline to user/kernel dma-debug space dump messages
(Desnes Nunes, Geert Uytterhoeve)
- swiotlb statistics improvements (Michael Kelley)
- misc cleanups (Petr Tesarik)
----------------------------------------------------------------
Desnes Nunes (2):
dma-debug: small dma_debug_entry's comment and variable name updates
dma-debug: add cacheline to user/kernel space dump messages
Doug Berger (1):
swiotlb: relocate PageHighMem test away from rmem_swiotlb_setup
Geert Uytterhoeven (1):
dma-debug: Use %pa to format phys_addr_t
Jiaxun Yang (3):
dma-mapping: provide a fallback dma_default_coherent
dma-mapping: provide CONFIG_ARCH_DMA_DEFAULT_COHERENT
of: address: always use dma_default_coherent for default coherency
Michael Kelley (2):
swiotlb: fix debugfs reporting of reserved memory pools
swiotlb: track and report io_tlb_used high water marks in debugfs
Petr Tesarik (2):
dma-direct: cleanup parameters to dma_direct_optimal_gfp_mask
swiotlb: Omit total_used and used_hiwater if !CONFIG_DEBUG_FS
arch/powerpc/Kconfig | 2 +-
arch/riscv/Kconfig | 2 +-
drivers/of/Kconfig | 4 --
drivers/of/address.c | 2 +-
include/linux/dma-map-ops.h | 2 +
include/linux/swiotlb.h | 9 +++
kernel/dma/Kconfig | 7 +++
kernel/dma/debug.c | 131 +++++++++++++++++++++++---------------------
kernel/dma/direct.c | 15 +++--
kernel/dma/mapping.c | 6 +-
kernel/dma/swiotlb.c | 97 ++++++++++++++++++++++++++++----
11 files changed, 189 insertions(+), 88 deletions(-)
next reply other threads:[~2023-04-28 6:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 6:10 Christoph Hellwig [this message]
2023-04-29 18:20 ` 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=ZEtjUWcp6qm4l+zl@infradead.org \
--to=hch@infradead.org \
--cc=iommu@lists.linux.dev \
--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®