From: patchwork-bot+linux-riscv@kernel.org <patchwork-bot+linux-riscv@kernel.org>
To: kvm-riscv@lists.infradead.org
Subject: [PATCH v3 0/6] riscv: Apply Zawrs when available
Date: Sun, 14 Jul 2024 20:30:33 +0000 [thread overview]
Message-ID: <172098903362.7439.8760600001594796975.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240426100820.14762-8-ajones@ventanamicro.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Fri, 26 Apr 2024 12:08:20 +0200 you 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.
>
> [...]
Here is the summary with links:
- [v3,1/6] riscv: Provide a definition for 'pause'
https://git.kernel.org/riscv/c/6da111574baf
- [v3,2/6] dt-bindings: riscv: Add Zawrs ISA extension description
https://git.kernel.org/riscv/c/6d5852811600
- [v3,3/6] riscv: Add Zawrs support for spinlocks
https://git.kernel.org/riscv/c/b8ddb0df30f9
- [v3,4/6] riscv: hwprobe: export Zawrs ISA extension
https://git.kernel.org/riscv/c/244c18fbf64a
- [v3,5/6] KVM: riscv: Support guest wrs.nto
https://git.kernel.org/riscv/c/86d6a86e59e3
- [v3,6/6] KVM: riscv: selftests: Add Zawrs extension to get-reg-list test
https://git.kernel.org/riscv/c/f2c43c61160e
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: Andrew Jones <ajones@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, kvm-riscv@lists.infradead.org,
devicetree@vger.kernel.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
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@sntech.de,
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: Sun, 14 Jul 2024 20:30:33 +0000 [thread overview]
Message-ID: <172098903362.7439.8760600001594796975.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240426100820.14762-8-ajones@ventanamicro.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Fri, 26 Apr 2024 12:08:20 +0200 you 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.
>
> [...]
Here is the summary with links:
- [v3,1/6] riscv: Provide a definition for 'pause'
https://git.kernel.org/riscv/c/6da111574baf
- [v3,2/6] dt-bindings: riscv: Add Zawrs ISA extension description
https://git.kernel.org/riscv/c/6d5852811600
- [v3,3/6] riscv: Add Zawrs support for spinlocks
https://git.kernel.org/riscv/c/b8ddb0df30f9
- [v3,4/6] riscv: hwprobe: export Zawrs ISA extension
https://git.kernel.org/riscv/c/244c18fbf64a
- [v3,5/6] KVM: riscv: Support guest wrs.nto
https://git.kernel.org/riscv/c/86d6a86e59e3
- [v3,6/6] KVM: riscv: selftests: Add Zawrs extension to get-reg-list test
https://git.kernel.org/riscv/c/f2c43c61160e
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
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Andrew Jones <ajones@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, kvm-riscv@lists.infradead.org,
devicetree@vger.kernel.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
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@sntech.de,
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: Sun, 14 Jul 2024 20:30:33 +0000 [thread overview]
Message-ID: <172098903362.7439.8760600001594796975.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240426100820.14762-8-ajones@ventanamicro.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Fri, 26 Apr 2024 12:08:20 +0200 you 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.
>
> [...]
Here is the summary with links:
- [v3,1/6] riscv: Provide a definition for 'pause'
https://git.kernel.org/riscv/c/6da111574baf
- [v3,2/6] dt-bindings: riscv: Add Zawrs ISA extension description
https://git.kernel.org/riscv/c/6d5852811600
- [v3,3/6] riscv: Add Zawrs support for spinlocks
https://git.kernel.org/riscv/c/b8ddb0df30f9
- [v3,4/6] riscv: hwprobe: export Zawrs ISA extension
https://git.kernel.org/riscv/c/244c18fbf64a
- [v3,5/6] KVM: riscv: Support guest wrs.nto
https://git.kernel.org/riscv/c/86d6a86e59e3
- [v3,6/6] KVM: riscv: selftests: Add Zawrs extension to get-reg-list test
https://git.kernel.org/riscv/c/f2c43c61160e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-07-14 20:30 UTC|newest]
Thread overview: 72+ 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 ` Andrew Jones
2024-04-26 10:08 ` Andrew Jones
2024-04-26 10:08 ` [PATCH v3 1/6] riscv: Provide a definition for 'pause' Andrew Jones
2024-04-26 10:08 ` Andrew Jones
2024-04-26 10:08 ` Andrew Jones
2024-04-26 10:08 ` [PATCH v3 2/6] dt-bindings: riscv: Add Zawrs ISA extension description Andrew Jones
2024-04-26 10:08 ` Andrew Jones
2024-04-26 10:08 ` Andrew Jones
2024-04-26 16:41 ` Conor Dooley
2024-04-26 16:41 ` Conor Dooley
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-04-26 10:08 ` Andrew Jones
2024-04-26 10:08 ` Andrew Jones
2024-07-29 13:43 ` Alexandre Ghiti
2024-07-29 13:43 ` Alexandre Ghiti
2024-07-29 13:43 ` Alexandre Ghiti
2024-07-29 14:01 ` Andrew Jones
2024-07-29 14:01 ` Andrew Jones
2024-07-29 14:01 ` Andrew Jones
2024-07-29 14:30 ` Alexandre Ghiti
2024-07-29 14:30 ` Alexandre Ghiti
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-04-26 10:08 ` Andrew Jones
2024-04-26 10:08 ` Andrew Jones
2024-06-18 13:48 ` Clément Léger
2024-06-18 13:48 ` Clément Léger
2024-06-18 13:48 ` Clément Léger
2024-06-18 16:01 ` Andrew Jones
2024-06-18 16:01 ` Andrew Jones
2024-06-18 16:01 ` Andrew Jones
2024-06-18 16:59 ` Conor Dooley
2024-06-18 16:59 ` Conor Dooley
2024-06-18 16:59 ` Conor Dooley
2024-06-18 17:05 ` Andrew Jones
2024-06-18 17:05 ` Andrew Jones
2024-06-18 17:05 ` Andrew Jones
2024-06-18 17:34 ` Conor Dooley
2024-06-18 17:34 ` Conor Dooley
2024-06-18 17:34 ` Conor Dooley
2024-07-15 15:45 ` Palmer Dabbelt
2024-07-15 15:45 ` Palmer Dabbelt
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-04-26 10:08 ` Andrew Jones
2024-04-26 10:08 ` Andrew Jones
2024-06-26 15:36 ` Anup Patel
2024-06-26 15:36 ` Anup Patel
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-04-26 10:08 ` Andrew Jones
2024-04-26 10:08 ` Andrew Jones
2024-06-26 15:37 ` Anup Patel
2024-06-26 15:37 ` Anup Patel
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-03 12:36 ` Andrew Jones
2024-06-03 12:36 ` Andrew Jones
2024-06-26 14:34 ` Palmer Dabbelt
2024-06-26 14:34 ` Palmer Dabbelt
2024-06-26 14:34 ` Palmer Dabbelt
2024-06-26 15:19 ` Andrew Jones
2024-06-26 15:19 ` Andrew Jones
2024-06-26 15:19 ` Andrew Jones
2024-06-26 15:38 ` Anup Patel
2024-06-26 15:38 ` Anup Patel
2024-06-26 15:38 ` Anup Patel
2024-07-14 20:30 ` patchwork-bot+linux-riscv [this message]
2024-07-14 20:30 ` patchwork-bot+linux-riscv
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=172098903362.7439.8760600001594796975.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=kvm-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 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.