Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <pjw@kernel.org>
To: linux-riscv@lists.infradead.org
Subject: [PATCH 0/3] riscv: mm: clean up and optimize some page table get-and-clear functions
Date: Wed, 19 Nov 2025 21:18:27 -0700	[thread overview]
Message-ID: <20251120042001.1766011-1-pjw@kernel.org> (raw)

This series implements some minor cleanups on the RISC-V page table
get-and-clear functions.  We continue the work from commit
546e42c8c6d94 ("riscv: Use an atomic xchg in
pudp_huge_get_and_clear()").  The two themes are:

- avoid atomic operations on non-SMP kernels

- use xchg() rather than atomic_long_xchg() on variables that aren't
  atomic_long_t

Tested on QEMU 10.0.6 on RV32 and RV64, SMP and !SMP, running kselftests.


- Paul

Paul Walmsley (3):
  riscv: mm: pmdp_huge_get_and_clear(): avoid atomic ops when
    !CONFIG_SMP
  riscv: mm: ptep_get_and_clear(): avoid atomic ops when !CONFIG_SMP
  riscv: mm: use xchg() on non-atomic_long_t variables, not
    atomic_long_xchg()

 arch/riscv/include/asm/pgtable.h | 16 ++++++++++++++--
 1 file changed, 14 insertions(+), 2 deletions(-)


base-commit: dcb6fa37fd7bc9c3d2b066329b0d27dedf8becaa
-- 
2.48.1


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

             reply	other threads:[~2025-11-20  4:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20  4:18 Paul Walmsley [this message]
2025-11-20  4:18 ` [PATCH 1/3] riscv: mm: pmdp_huge_get_and_clear(): avoid atomic ops when !CONFIG_SMP Paul Walmsley
2025-11-20  4:18 ` [PATCH 2/3] riscv: mm: ptep_get_and_clear(): " Paul Walmsley
2025-11-20  4:18 ` [PATCH 3/3] riscv: mm: use xchg() on non-atomic_long_t variables, not atomic_long_xchg() Paul Walmsley
2025-11-20  4:30 ` [PATCH 0/3] riscv: mm: clean up and optimize some page table get-and-clear functions patchwork-bot+linux-riscv

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=20251120042001.1766011-1-pjw@kernel.org \
    --to=pjw@kernel.org \
    --cc=linux-riscv@lists.infradead.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