From: Andrew Jones <ajones@ventanamicro.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: linux-riscv@lists.infradead.org, kvm-riscv@lists.infradead.org,
devicetree@vger.kernel.org,
Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, Conor Dooley <conor.dooley@microchip.com>,
anup@brainfault.org, atishp@atishpatra.org, robh@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
christoph.muellner@vrull.eu, Heiko Stuebner <heiko@sntech.de>,
Charlie Jenkins <charlie@rivosinc.com>,
David.Laight@aculab.com, parri.andrea@gmail.com,
luxu.kernel@bytedance.com
Subject: Re: [PATCH v3 0/6] riscv: Apply Zawrs when available
Date: Wed, 26 Jun 2024 17:19:42 +0200 [thread overview]
Message-ID: <20240626-203887902f79278e20134dea@orel> (raw)
In-Reply-To: <mhng-4fc810f5-fd3a-44f3-bd78-9a6b7bf2ab77@palmer-ri-x1c9>
On Wed, Jun 26, 2024 at 07:34:48AM GMT, Palmer Dabbelt wrote:
> On Mon, 03 Jun 2024 05:36:42 PDT (-0700), ajones@ventanamicro.com wrote:
> > Hi Palmer,
> >
> > I submit our concerns of wrs.nto to RVI ARC for consideration. They
> > discussed it but don't believe there's a need for concern. The
> > expectation is that there will always be enough interrupt activity
> > and that those interrupts with activity will not likely be locally
> > disabled.
> >
> > Can we consider this series for 6.10?
>
> Sorry I forgot about this one, Anup just brought it up in the patchwork
> meeting. He's going to ack the KVM bits, then I'll pick it up.
Thanks Palmer!
drew
>
> >
> > Thanks,
> > drew
> >
> > On Fri, Apr 26, 2024 at 12:08:20PM GMT, Andrew Jones wrote:
> > > Zawrs provides two instructions (wrs.nto and wrs.sto), where both are
> > > meant to allow the hart to enter a low-power state while waiting on a
> > > store to a memory location. The instructions also both wait an
> > > implementation-defined "short" duration (unless the implementation
> > > terminates the stall for another reason). The difference is that while
> > > wrs.sto will terminate when the duration elapses, wrs.nto, depending on
> > > configuration, will either just keep waiting or an ILL exception will be
> > > raised. Linux will use wrs.nto, so if platforms have an implementation
> > > which falls in the "just keep waiting" category (which is not expected),
> > > then it should _not_ advertise Zawrs in the hardware description.
> > >
> > > Like wfi (and with the same {m,h}status bits to configure it), when
> > > wrs.nto is configured to raise exceptions it's expected that the higher
> > > privilege level will see the instruction was a wait instruction, do
> > > something, and then resume execution following the instruction. For
> > > example, KVM does configure exceptions for wfi (hstatus.VTW=1) and
> > > therefore also for wrs.nto. KVM does this for wfi since it's better to
> > > allow other tasks to be scheduled while a VCPU waits for an interrupt.
> > > For waits such as those where wrs.nto/sto would be used, which are
> > > typically locks, it is also a good idea for KVM to be involved, as it
> > > can attempt to schedule the lock holding VCPU.
> > >
> > > This series starts with Christoph's addition of the riscv
> > > smp_cond_load_relaxed function which applies wrs.sto when available.
> > > That patch has been reworked to use wrs.nto and to use the same approach
> > > as Arm for the wait loop, since we can't have arbitrary C code between
> > > the load-reserved and the wrs. Then, hwprobe support is added (since the
> > > instructions are also usable from usermode), and finally KVM is
> > > taught about wrs.nto, allowing guests to see and use the Zawrs
> > > extension.
> > >
> > > We still don't have test results from hardware, and it's not possible to
> > > prove that using Zawrs is a win when testing on QEMU, not even when
> > > oversubscribing VCPUs to guests. However, it is possible to use KVM
> > > selftests to force a scenario where we can prove Zawrs does its job and
> > > does it well. [4] is a test which does this and, on my machine, without
> > > Zawrs it takes 16 seconds to complete and with Zawrs it takes 0.25
> > > seconds.
> > >
> > > This series is also available here [1]. In order to use QEMU for testing
> > > a build with [2] is needed. In order to enable guests to use Zawrs with
> > > KVM using kvmtool, the branch at [3] may be used.
> > >
> > > [1] https://github.com/jones-drew/linux/commits/riscv/zawrs-v3/
> > > [2] https://lore.kernel.org/all/20240312152901.512001-2-ajones@ventanamicro.com/
> > > [3] https://github.com/jones-drew/kvmtool/commits/riscv/zawrs/
> > > [4] https://github.com/jones-drew/linux/commit/cb2beccebcece10881db842ed69bdd5715cfab5d
> > >
> > > Thanks,
> > > drew
> > >
> > > v3:
> > > - Moved comment about expected termination from the DT binding text
> > > to a code comment.
> > >
> > > v2:
> > > - Added DT bindings patch with additional Linux specifications due
> > > to wrs.nto potentially never terminating, as suggested by Palmer
> > > - Added patch to share pause insn definition
> > > - Rework main Zawrs support patch to use Arm approach (which is
> > > also the approach that Andrea Parri suggested)
> > > - Dropped the riscv implementation of smp_cond_load_acquire().
> > > afaict, the generic implementation, which will use the riscv
> > > implementation of smp_cond_load_relaxed() is sufficient for riscv.
> > > - The rework was large enough (IMO) to drop Heiko's s-o-b and to
> > > add myself as a co-developer
> > >
> > >
> > > Andrew Jones (5):
> > > riscv: Provide a definition for 'pause'
> > > dt-bindings: riscv: Add Zawrs ISA extension description
> > > riscv: hwprobe: export Zawrs ISA extension
> > > KVM: riscv: Support guest wrs.nto
> > > KVM: riscv: selftests: Add Zawrs extension to get-reg-list test
> > >
> > > Christoph M??llner (1):
> > > riscv: Add Zawrs support for spinlocks
> > >
> > > Documentation/arch/riscv/hwprobe.rst | 4 ++
> > > .../devicetree/bindings/riscv/extensions.yaml | 7 +++
> > > arch/riscv/Kconfig | 20 ++++---
> > > arch/riscv/Makefile | 3 -
> > > arch/riscv/include/asm/barrier.h | 45 +++++++++-----
> > > arch/riscv/include/asm/cmpxchg.h | 58 +++++++++++++++++++
> > > arch/riscv/include/asm/hwcap.h | 1 +
> > > arch/riscv/include/asm/insn-def.h | 4 ++
> > > arch/riscv/include/asm/kvm_host.h | 1 +
> > > arch/riscv/include/asm/vdso/processor.h | 8 +--
> > > arch/riscv/include/uapi/asm/hwprobe.h | 1 +
> > > arch/riscv/include/uapi/asm/kvm.h | 1 +
> > > arch/riscv/kernel/cpufeature.c | 1 +
> > > arch/riscv/kernel/sys_hwprobe.c | 1 +
> > > arch/riscv/kvm/vcpu.c | 1 +
> > > arch/riscv/kvm/vcpu_insn.c | 15 +++++
> > > arch/riscv/kvm/vcpu_onereg.c | 2 +
> > > .../selftests/kvm/riscv/get-reg-list.c | 4 ++
> > > 18 files changed, 146 insertions(+), 31 deletions(-)
> > >
> > > --
> > > 2.44.0
> > >
next prev parent reply other threads:[~2024-06-26 15:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 10:08 [PATCH v3 0/6] riscv: Apply Zawrs when available Andrew Jones
2024-04-26 10:08 ` [PATCH v3 1/6] riscv: Provide a definition for 'pause' Andrew Jones
2024-04-26 10:08 ` [PATCH v3 2/6] dt-bindings: riscv: Add Zawrs ISA extension description Andrew Jones
2024-04-26 16:41 ` Conor Dooley
2024-04-26 10:08 ` [PATCH v3 3/6] riscv: Add Zawrs support for spinlocks Andrew Jones
2024-07-29 13:43 ` Alexandre Ghiti
2024-07-29 14:01 ` Andrew Jones
2024-07-29 14:30 ` Alexandre Ghiti
2024-04-26 10:08 ` [PATCH v3 4/6] riscv: hwprobe: export Zawrs ISA extension Andrew Jones
2024-06-18 13:48 ` Clément Léger
2024-06-18 16:01 ` Andrew Jones
2024-06-18 16:59 ` Conor Dooley
2024-06-18 17:05 ` Andrew Jones
2024-06-18 17:34 ` Conor Dooley
2024-07-15 15:45 ` Palmer Dabbelt
2024-04-26 10:08 ` [PATCH v3 5/6] KVM: riscv: Support guest wrs.nto Andrew Jones
2024-06-26 15:36 ` Anup Patel
2024-04-26 10:08 ` [PATCH v3 6/6] KVM: riscv: selftests: Add Zawrs extension to get-reg-list test Andrew Jones
2024-06-26 15:37 ` Anup Patel
2024-06-03 12:36 ` [PATCH v3 0/6] riscv: Apply Zawrs when available Andrew Jones
2024-06-26 14:34 ` Palmer Dabbelt
2024-06-26 15:19 ` Andrew Jones [this message]
2024-06-26 15:38 ` Anup Patel
2024-07-14 20:30 ` 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=20240626-203887902f79278e20134dea@orel \
--to=ajones@ventanamicro.com \
--cc=David.Laight@aculab.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@atishpatra.org \
--cc=charlie@rivosinc.com \
--cc=christoph.muellner@vrull.eu \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kvm-riscv@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=luxu.kernel@bytedance.com \
--cc=palmer@dabbelt.com \
--cc=parri.andrea@gmail.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.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).