From: patchwork-bot+linux-riscv@kernel.org
To: Evan Green <evan@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, palmer@rivosinc.com,
rdunlap@infradead.org, heiko@sntech.de,
linux-doc@vger.kernel.org, bjorn@rivosinc.com,
conor.dooley@microchip.com, guoren@kernel.org,
jszhang@kernel.org, samuel@sholland.org,
jeeheng.sia@starfivetech.com, maz@kernel.org,
masahiroy@kernel.org, greentime.hu@sifive.com,
shosie@rivosinc.com, ajones@ventanamicro.com,
aou@eecs.berkeley.edu, alexghiti@rivosinc.com,
leyfoon.tan@starfivetech.com, paul.walmsley@sifive.com,
apatel@ventanamicro.com, corbet@lwn.net,
linux-kernel@vger.kernel.org, xianting.tian@linux.alibaba.com,
David.Laight@aculab.com, palmer@dabbelt.com,
andy.chiu@sifive.com
Subject: Re: [PATCH v4 0/2] RISC-V: Probe for misaligned access speed
Date: Wed, 30 Aug 2023 20:30:28 +0000 [thread overview]
Message-ID: <169342742851.1913.116474602408550824.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230818194136.4084400-1-evan@rivosinc.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Fri, 18 Aug 2023 12:41:34 -0700 you wrote:
> The current setting for the hwprobe bit indicating misaligned access
> speed is controlled by a vendor-specific feature probe function. This is
> essentially a per-SoC table we have to maintain on behalf of each vendor
> going forward. Let's convert that instead to something we detect at
> runtime.
>
> We have two assembly routines at the heart of our probe: one that
> does a bunch of word-sized accesses (without aligning its input buffer),
> and the other that does byte accesses. If we can move a larger number of
> bytes using misaligned word accesses than we can with the same amount of
> time doing byte accesses, then we can declare misaligned accesses as
> "fast".
>
> [...]
Here is the summary with links:
- [v4,1/2] RISC-V: Probe for unaligned access speed
https://git.kernel.org/riscv/c/b98673c5b037
- [v4,2/2] RISC-V: alternative: Remove feature_probe_func
https://git.kernel.org/riscv/c/b6e3f6e009a1
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-08-30 23:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 19:41 [PATCH v4 0/2] RISC-V: Probe for misaligned access speed Evan Green
2023-08-18 19:41 ` [PATCH v4 1/2] RISC-V: Probe for unaligned " Evan Green
2023-09-13 12:36 ` Geert Uytterhoeven
2023-09-13 17:46 ` Evan Green
2023-09-14 7:32 ` Geert Uytterhoeven
2023-09-14 8:46 ` David Laight
2023-09-14 15:01 ` Evan Green
2023-09-14 15:55 ` David Laight
2023-09-14 16:36 ` Evan Green
2023-09-15 7:57 ` David Laight
2023-09-15 16:47 ` Evan Green
2023-10-19 6:37 ` Geert Uytterhoeven
2023-10-19 7:51 ` Lad, Prabhakar
2023-08-18 19:41 ` [PATCH v4 2/2] RISC-V: alternative: Remove feature_probe_func Evan Green
2023-08-30 20:30 ` 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=169342742851.1913.116474602408550824.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=David.Laight@aculab.com \
--cc=ajones@ventanamicro.com \
--cc=alexghiti@rivosinc.com \
--cc=andy.chiu@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=bjorn@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=corbet@lwn.net \
--cc=evan@rivosinc.com \
--cc=greentime.hu@sifive.com \
--cc=guoren@kernel.org \
--cc=heiko@sntech.de \
--cc=jeeheng.sia@starfivetech.com \
--cc=jszhang@kernel.org \
--cc=leyfoon.tan@starfivetech.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=masahiroy@kernel.org \
--cc=maz@kernel.org \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=rdunlap@infradead.org \
--cc=samuel@sholland.org \
--cc=shosie@rivosinc.com \
--cc=xianting.tian@linux.alibaba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox