From: patchwork-bot+linux-riscv@kernel.org
To: Alexandre Ghiti <alexghiti@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, linux@armlinux.org.uk,
ryan.roberts@arm.com, glider@google.com, elver@google.com,
dvyukov@google.com, paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, anup@brainfault.org,
atishp@atishpatra.org, ardb@kernel.org, ryabinin.a.a@gmail.com,
andreyknvl@gmail.com, vincenzo.frascino@arm.com,
kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
linux-efi@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2 0/4] riscv: Use READ_ONCE()/WRITE_ONCE() for pte accesses
Date: Fri, 05 Jan 2024 21:50:27 +0000 [thread overview]
Message-ID: <170449142778.26226.7492189738418488414.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231213203001.179237-1-alexghiti@rivosinc.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 13 Dec 2023 21:29:57 +0100 you wrote:
> This series is a follow-up for riscv of a recent series from Ryan [1] which
> converts all direct dereferences of pte_t into a ptet_get() access.
>
> The goal here for riscv is to use READ_ONCE()/WRITE_ONCE() for all page
> table entries accesses to avoid any compiler transformation when the
> hardware can concurrently modify the page tables entries (A/D bits for
> example).
>
> [...]
Here is the summary with links:
- [v2,1/4] riscv: Use WRITE_ONCE() when setting page table entries
https://git.kernel.org/riscv/c/c30fa83b4989
- [v2,2/4] mm: Introduce pudp/p4dp/pgdp_get() functions
https://git.kernel.org/riscv/c/eba2591d99d1
- [v2,3/4] riscv: mm: Only compile pgtable.c if MMU
https://git.kernel.org/riscv/c/d6508999d188
- [v2,4/4] riscv: Use accessors to page table entries instead of direct dereference
https://git.kernel.org/riscv/c/edf955647269
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Alexandre Ghiti <alexghiti@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, linux@armlinux.org.uk,
ryan.roberts@arm.com, glider@google.com, elver@google.com,
dvyukov@google.com, paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, anup@brainfault.org,
atishp@atishpatra.org, ardb@kernel.org, ryabinin.a.a@gmail.com,
andreyknvl@gmail.com, vincenzo.frascino@arm.com,
kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
linux-efi@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2 0/4] riscv: Use READ_ONCE()/WRITE_ONCE() for pte accesses
Date: Fri, 05 Jan 2024 21:50:27 +0000 [thread overview]
Message-ID: <170449142778.26226.7492189738418488414.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231213203001.179237-1-alexghiti@rivosinc.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 13 Dec 2023 21:29:57 +0100 you wrote:
> This series is a follow-up for riscv of a recent series from Ryan [1] which
> converts all direct dereferences of pte_t into a ptet_get() access.
>
> The goal here for riscv is to use READ_ONCE()/WRITE_ONCE() for all page
> table entries accesses to avoid any compiler transformation when the
> hardware can concurrently modify the page tables entries (A/D bits for
> example).
>
> [...]
Here is the summary with links:
- [v2,1/4] riscv: Use WRITE_ONCE() when setting page table entries
https://git.kernel.org/riscv/c/c30fa83b4989
- [v2,2/4] mm: Introduce pudp/p4dp/pgdp_get() functions
https://git.kernel.org/riscv/c/eba2591d99d1
- [v2,3/4] riscv: mm: Only compile pgtable.c if MMU
https://git.kernel.org/riscv/c/d6508999d188
- [v2,4/4] riscv: Use accessors to page table entries instead of direct dereference
https://git.kernel.org/riscv/c/edf955647269
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-01-05 21:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 20:29 [PATCH v2 0/4] riscv: Use READ_ONCE()/WRITE_ONCE() for pte accesses Alexandre Ghiti
2023-12-13 20:29 ` Alexandre Ghiti
2023-12-13 20:29 ` [PATCH v2 1/4] riscv: Use WRITE_ONCE() when setting page table entries Alexandre Ghiti
2023-12-13 20:29 ` Alexandre Ghiti
2023-12-13 20:29 ` [PATCH v2 2/4] mm: Introduce pudp/p4dp/pgdp_get() functions Alexandre Ghiti
2023-12-13 20:29 ` Alexandre Ghiti
2023-12-13 20:30 ` [PATCH v2 3/4] riscv: mm: Only compile pgtable.c if MMU Alexandre Ghiti
2023-12-13 20:30 ` Alexandre Ghiti
2023-12-13 20:30 ` [PATCH v2 4/4] riscv: Use accessors to page table entries instead of direct dereference Alexandre Ghiti
2023-12-13 20:30 ` Alexandre Ghiti
2023-12-14 5:34 ` Anup Patel
2023-12-14 5:34 ` Anup Patel
2024-01-05 21:50 ` patchwork-bot+linux-riscv [this message]
2024-01-05 21:50 ` [PATCH v2 0/4] riscv: Use READ_ONCE()/WRITE_ONCE() for pte accesses 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=170449142778.26226.7492189738418488414.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alexghiti@rivosinc.com \
--cc=andreyknvl@gmail.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=ardb@kernel.org \
--cc=atishp@atishpatra.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=ryabinin.a.a@gmail.com \
--cc=ryan.roberts@arm.com \
--cc=vincenzo.frascino@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.