From: patchwork-bot+linux-riscv@kernel.org
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, corbet@lwn.net,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, costa.shul@redhat.com,
conor.dooley@microchip.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: RISC-V: uabi: Only scalar misaligned loads are supported
Date: Thu, 30 May 2024 21:10:30 +0000 [thread overview]
Message-ID: <171710343056.6624.2242126513528878113.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240524185600.5919-1-palmer@rivosinc.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Fri, 24 May 2024 11:56:00 -0700 you wrote:
> From: Palmer Dabbelt <palmer@rivosinc.com>
>
> We're stuck supporting scalar misaligned loads in userspace because they
> were part of the ISA at the time we froze the uABI. That wasn't the
> case for vector misaligned accesses, so depending on them
> unconditionally is a userspace bug. All extant vector hardware traps on
> these misaligned accesses.
>
> [...]
Here is the summary with links:
- Documentation: RISC-V: uabi: Only scalar misaligned loads are supported
https://git.kernel.org/riscv/c/982a7eb97be6
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
prev parent reply other threads:[~2024-05-30 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 18:56 [PATCH] Documentation: RISC-V: uabi: Only scalar misaligned loads are supported Palmer Dabbelt
2024-05-24 19:14 ` Conor Dooley
2024-05-30 21:10 ` 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=171710343056.6624.2242126513528878113.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=corbet@lwn.net \
--cc=costa.shul@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.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