From: Paul Walmsley <pjw@kernel.org>
To: Naohiko Shimizu <naohiko.shimizu@gmail.com>
Cc: pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
alex@ghiti.fr, anup@brainfault.org, atish.patra@linux.dev,
daniel.lezcano@linaro.org, tglx@linutronix.de,
nick.hu@sifive.com, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
kvm-riscv@lists.infradead.org
Subject: Re: [PATCH v3 0/3] riscv: fix timer update hazards on RV32
Date: Wed, 14 Jan 2026 17:39:02 -0700 (MST) [thread overview]
Message-ID: <10a102b9-1dd1-c5ca-66e4-f02794a84a93@kernel.org> (raw)
In-Reply-To: <20260104135938.524-1-naohiko.shimizu@gmail.com>
On Sun, 4 Jan 2026, Naohiko Shimizu wrote:
> This patch series fixes timer register update hazards on RV32 for
> clocksource, KVM, and suspend/resume paths by adopting the 3-step
> update sequence recommended by the RISC-V Privileged Specification.
>
> Changes in v3:
> - Dropped redundant subject line from commit descriptions.
> - Added Fixes tags for all patches.
> - Moved Signed-off-by tags to the end of commit messages.
>
> Changes in v2:
> - Added detailed architectural background to commit messages.
> - Added KVM and suspend/resume cases.
>
> Naohiko Shimizu (3):
> riscv: clocksource: Fix stimecmp update hazard on RV32
> riscv: kvm: Fix vstimecmp update hazard on RV32
> riscv: suspend: Fix stimecmp update hazard on RV32
>
> arch/riscv/kernel/suspend.c | 3 ++-
> arch/riscv/kvm/vcpu_timer.c | 6 ++++--
> drivers/clocksource/timer-riscv.c | 3 ++-
> 3 files changed, 8 insertions(+), 4 deletions(-)
Thanks, queued for v6.19-rc.
- Paul
next prev parent reply other threads:[~2026-01-15 0:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 13:59 Naohiko Shimizu
2026-01-04 13:59 ` [PATCH v3 1/3] riscv: clocksource: Fix stimecmp update hazard " Naohiko Shimizu
2026-01-05 4:31 ` Anup Patel
2026-01-04 13:59 ` [PATCH v3 2/3] riscv: kvm: Fix vstimecmp " Naohiko Shimizu
2026-01-05 4:31 ` Anup Patel
2026-01-15 1:11 ` Naohiko Shimizu
2026-01-04 13:59 ` [PATCH v3 3/3] riscv: suspend: Fix stimecmp " Naohiko Shimizu
2026-01-05 4:31 ` Anup Patel
2026-01-15 0:39 ` Paul Walmsley [this message]
2026-01-15 1:11 ` [PATCH v3 0/3] riscv: fix timer update hazards " Naohiko Shimizu
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=10a102b9-1dd1-c5ca-66e4-f02794a84a93@kernel.org \
--to=pjw@kernel.org \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@linux.dev \
--cc=daniel.lezcano@linaro.org \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=naohiko.shimizu@gmail.com \
--cc=nick.hu@sifive.com \
--cc=palmer@dabbelt.com \
--cc=tglx@linutronix.de \
/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®