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, conor.dooley@microchip.com,
paul.walmsley@sifive.com, palmer@dabbelt.com,
sudip.mukherjee@codethink.co.uk, ben.dooks@codethink.co.uk,
atishp@rivosinc.com, aou@eecs.berkeley.edu,
apatel@ventanamicro.com, krzysztof.kozlowski+dt@linaro.org,
robh@kernel.org, jszhang@kernel.org, heiko@sntech.de
Subject: Re: [PATCH v6 0/8] RISC-V: Apply Zicboz to clear_page
Date: Sat, 18 Mar 2023 01:00:21 +0000 [thread overview]
Message-ID: <167910122129.24496.10588514847374462522.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230224162631.405473-1-ajones@ventanamicro.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Fri, 24 Feb 2023 17:26:23 +0100 you wrote:
> When the Zicboz extension is available we can more rapidly zero naturally
> aligned Zicboz block sized chunks of memory. As pages are always page
> aligned and are larger than any Zicboz block size will be, then
> clear_page() appears to be a good candidate for the extension. While cycle
> count and energy consumption should also be considered, we can be pretty
> certain that implementing clear_page() with the Zicboz extension is a win
> by comparing the new dynamic instruction count with its current count[1].
> Doing so we see that the new count is just over a quarter of the old count
> (see patch6's commit message for more details).
>
> [...]
Here is the summary with links:
- [v6,1/8] RISC-V: alternatives: Support patching multiple insns in assembly
https://git.kernel.org/riscv/c/0b2f658f5370
- [v6,2/8] RISC-V: Factor out body of riscv_init_cbom_blocksize loop
https://git.kernel.org/riscv/c/8b05e7d0408a
- [v6,3/8] dt-bindings: riscv: Document cboz-block-size
https://git.kernel.org/riscv/c/ea20f117ab99
- [v6,4/8] RISC-V: Add Zicboz detection and block size parsing
https://git.kernel.org/riscv/c/7ea5a73617e9
- [v6,5/8] RISC-V: cpufeatures: Put the upper 16 bits of patch ID to work
https://git.kernel.org/riscv/c/d25f256332cc
- [v6,6/8] RISC-V: Use Zicboz in clear_page when available
https://git.kernel.org/riscv/c/ab0f77465e3e
- [v6,7/8] RISC-V: KVM: Provide UAPI for Zicboz block size
https://git.kernel.org/riscv/c/665fd8862413
- [v6,8/8] RISC-V: KVM: Expose Zicboz to the guest
https://git.kernel.org/riscv/c/b20f67994f35
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-03-18 1:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 16:26 [PATCH v6 0/8] RISC-V: Apply Zicboz to clear_page Andrew Jones
2023-02-24 16:26 ` [PATCH v6 1/8] RISC-V: alternatives: Support patching multiple insns in assembly Andrew Jones
2023-02-24 16:26 ` [PATCH v6 2/8] RISC-V: Factor out body of riscv_init_cbom_blocksize loop Andrew Jones
2023-02-24 16:26 ` [PATCH v6 3/8] dt-bindings: riscv: Document cboz-block-size Andrew Jones
2023-02-24 16:26 ` [PATCH v6 4/8] RISC-V: Add Zicboz detection and block size parsing Andrew Jones
2023-02-24 16:26 ` [PATCH v6 5/8] RISC-V: cpufeatures: Put the upper 16 bits of patch ID to work Andrew Jones
2023-02-24 16:26 ` [PATCH v6 6/8] RISC-V: Use Zicboz in clear_page when available Andrew Jones
2023-02-24 16:26 ` [PATCH v6 7/8] RISC-V: KVM: Provide UAPI for Zicboz block size Andrew Jones
2023-02-24 16:26 ` [PATCH v6 8/8] RISC-V: KVM: Expose Zicboz to the guest Andrew Jones
2023-03-15 4:38 ` Palmer Dabbelt
2023-03-15 4:54 ` Anup Patel
2023-03-15 4:35 ` [PATCH v6 0/8] RISC-V: Apply Zicboz to clear_page Palmer Dabbelt
2023-03-15 8:53 ` Andrew Jones
2023-03-18 1:00 ` patchwork-bot+linux-riscv [this message]
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=167910122129.24496.10588514847374462522.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=atishp@rivosinc.com \
--cc=ben.dooks@codethink.co.uk \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jszhang@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kvm-riscv@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=sudip.mukherjee@codethink.co.uk \
/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).