From: Paul Walmsley <pjw@kernel.org>
To: Andy Chiu <tchiu@tenstorrent.com>
Cc: Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
linux-riscv@lists.infradead.org, andybnac@gmail.com,
dfustini@oss.tenstorrent.com, greentime.hu@sifive.com,
linux-kernel@vger.kernel.org, olof@lixom.net
Subject: Re: [PATCH v1 0/2] riscv: runtime enablement for native misaligned ucopy
Date: Tue, 6 Oct 2026 04:16:29 -0600 (MDT) [thread overview]
Message-ID: <2d08eaa4-c7da-04ce-e3d4-7cddd336db12@kernel.org> (raw)
In-Reply-To: <20260911182402.1434257-1-tchiu@tenstorrent.com>
On Fri, 11 Sep 2026, Andy Chiu wrote:
> This series is the continued series for commit b94cec5761d2 ("riscv:
> skip software algning code for HAVE_EFFICIENT_UNALIGNED_ACCESS") that
> makes the optimization available to distro kernels compiled without
> NONPORTABLE config. Now, the kernel can skip the software aligning code
> in ucopy after fast unaligned access is detected at runtime.
Thanks, queued for v7.4.
- Paul
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-10-06 10:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 18:23 [PATCH v1 0/2] riscv: runtime enablement for native misaligned ucopy Andy Chiu
2026-09-11 18:23 ` [PATCH v1 1/2] riscv: introduce assembly version of jump table Andy Chiu
2026-09-11 18:24 ` [PATCH v1 2/2] riscv: optmize ucopy for has_fast_unaligned_accesses Andy Chiu
2026-10-06 9:40 ` [PATCH v1 0/2] riscv: runtime enablement for native misaligned ucopy patchwork-bot+linux-riscv
2026-10-06 10:16 ` Paul Walmsley [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=2d08eaa4-c7da-04ce-e3d4-7cddd336db12@kernel.org \
--to=pjw@kernel.org \
--cc=alex@ghiti.fr \
--cc=andybnac@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=dfustini@oss.tenstorrent.com \
--cc=greentime.hu@sifive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=olof@lixom.net \
--cc=palmer@dabbelt.com \
--cc=tchiu@tenstorrent.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 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.