From: Xu Lu <luxu.kernel@bytedance.com>
To: akpm@linux-foundation.org, jhubbard@nvidia.com,
kirill.shutemov@linux.intel.com, tjeznach@rivosinc.com,
joro@8bytes.org, will@kernel.org, robin.murphy@arm.com
Cc: lihangjing@bytedance.com, xieyongji@bytedance.com,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Xu Lu <luxu.kernel@bytedance.com>
Subject: [PATCH RESEND v2 0/4] riscv: iommu: Support Svnapot
Date: Tue, 18 Mar 2025 11:59:26 +0800 [thread overview]
Message-ID: <20250318035930.11855-1-luxu.kernel@bytedance.com> (raw)
According to the RISC-V IOMMU hardware spec, the IOMMU implementation
has the same translation process as MMU and supports Svnapot standard
extension as well. These patches add support for Svnapot in the IOMMU
driver to make 64K also an available page size during DMA mapping.
Changes in V2:
1. Supply more details about huge pte issue in follow_page_pte().
2. Fix some style problems.
Xu Lu (4):
mm/gup: Add huge pte handling logic in follow_page_pte()
iommu/riscv: Use pte_t to represent page table entry
iommu/riscv: Introduce IOMMU page table lock
iommu/riscv: Add support for Svnapot
arch/riscv/include/asm/pgtable.h | 6 +
drivers/iommu/riscv/iommu.c | 258 +++++++++++++++++++++++++------
include/linux/pgtable.h | 8 +
mm/gup.c | 17 +-
4 files changed, 233 insertions(+), 56 deletions(-)
--
2.20.1
next reply other threads:[~2025-03-18 3:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 3:59 Xu Lu [this message]
2025-03-18 3:59 ` [PATCH RESEND v2 1/4] mm/gup: Add huge pte handling logic in follow_page_pte() Xu Lu
2025-03-18 3:59 ` [PATCH RESEND v2 2/4] iommu/riscv: Use pte_t to represent page table entry Xu Lu
2025-03-18 3:59 ` [PATCH RESEND v2 3/4] iommu/riscv: Introduce IOMMU page table lock Xu Lu
2025-04-01 15:19 ` Jason Gunthorpe
2025-03-18 3:59 ` [PATCH RESEND v2 4/4] iommu/riscv: Add support for Svnapot Xu Lu
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=20250318035930.11855-1-luxu.kernel@bytedance.com \
--to=luxu.kernel@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=jhubbard@nvidia.com \
--cc=joro@8bytes.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=lihangjing@bytedance.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=robin.murphy@arm.com \
--cc=tjeznach@rivosinc.com \
--cc=will@kernel.org \
--cc=xieyongji@bytedance.com \
/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