From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: linuxppc-dev@lists.ozlabs.org
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org
Subject: [PATCH kernel 0/2] powerpc/dma: Fallback to dma_ops when persistent memory present
Date: Wed, 21 Oct 2020 14:20:24 +1100 [thread overview]
Message-ID: <20201021032026.45030-1-aik@ozlabs.ru> (raw)
This allows mixing direct DMA (to/from RAM) and
IOMMU (to/from apersistent memory) on the PPC64/pseries
platform. This was supposed to be a single patch but
unexpected move of direct DMA functions happened.
This is based on sha1
7cf726a59435 Linus Torvalds "Merge tag 'linux-kselftest-kunit-5.10-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest".
Please comment. Thanks.
Alexey Kardashevskiy (2):
Revert "dma-mapping: move large parts of <linux/dma-direct.h> to
kernel/dma"
powerpc/dma: Fallback to dma_ops when persistent memory present
include/linux/dma-direct.h | 106 ++++++++++++++++++++++
kernel/dma/direct.h | 119 -------------------------
arch/powerpc/kernel/dma-iommu.c | 68 +++++++++++++-
arch/powerpc/platforms/pseries/iommu.c | 41 +++++++--
kernel/dma/direct.c | 2 +-
kernel/dma/mapping.c | 2 +-
6 files changed, 207 insertions(+), 131 deletions(-)
delete mode 100644 kernel/dma/direct.h
--
2.17.1
next reply other threads:[~2020-10-21 3:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 3:20 Alexey Kardashevskiy [this message]
2020-10-21 3:20 ` [PATCH kernel 1/2] Revert "dma-mapping: move large parts of <linux/dma-direct.h> to kernel/dma" Alexey Kardashevskiy
2020-10-21 3:20 ` [PATCH kernel 2/2] powerpc/dma: Fallback to dma_ops when persistent memory present Alexey Kardashevskiy
2020-10-27 8:36 ` [PATCH kernel 0/2] " Christoph Hellwig
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=20201021032026.45030-1-aik@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).