From: Evan Green <evan@rivosinc.com>
To: Charlie Jenkins <charlie@rivosinc.com>
Cc: "Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Jisheng Zhang" <jszhang@kernel.org>,
"Clément Léger" <cleger@rivosinc.com>,
"Eric Biggers" <ebiggers@kernel.org>,
"Elliot Berman" <quic_eberman@quicinc.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] riscv: lib: Introduce has_fast_misaligned_access function
Date: Wed, 14 Feb 2024 09:24:47 -0500 [thread overview]
Message-ID: <CALs-HsvLH_QYUViSBuBgF4vW_X4CJ3M8tgOVfAHi5WdVXx54fQ@mail.gmail.com> (raw)
In-Reply-To: <20240202-disable_misaligned_probe_config-v3-1-c44f91f03bb6@rivosinc.com>
On Fri, Feb 2, 2024 at 6:54 PM Charlie Jenkins <charlie@rivosinc.com> wrote:
>
> Create has_fast_misaligned_access to avoid needing to explicitly check
> the fast_misaligned_access_speed_key static key.
>
> Signed-off-by: Charlie Jenkins <charlie@rivosinc.com>
Reviewed-by: Evan Green <evan@rivosinc.com>
WARNING: multiple messages have this Message-ID (diff)
From: Evan Green <evan@rivosinc.com>
To: Charlie Jenkins <charlie@rivosinc.com>
Cc: "Albert Ou" <aou@eecs.berkeley.edu>,
linux-kernel@vger.kernel.org,
"Eric Biggers" <ebiggers@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Jisheng Zhang" <jszhang@kernel.org>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Clément Léger" <cleger@rivosinc.com>,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v3 1/2] riscv: lib: Introduce has_fast_misaligned_access function
Date: Wed, 14 Feb 2024 09:24:47 -0500 [thread overview]
Message-ID: <CALs-HsvLH_QYUViSBuBgF4vW_X4CJ3M8tgOVfAHi5WdVXx54fQ@mail.gmail.com> (raw)
In-Reply-To: <20240202-disable_misaligned_probe_config-v3-1-c44f91f03bb6@rivosinc.com>
On Fri, Feb 2, 2024 at 6:54 PM Charlie Jenkins <charlie@rivosinc.com> wrote:
>
> Create has_fast_misaligned_access to avoid needing to explicitly check
> the fast_misaligned_access_speed_key static key.
>
> Signed-off-by: Charlie Jenkins <charlie@rivosinc.com>
Reviewed-by: Evan Green <evan@rivosinc.com>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-02-14 14:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 23:54 [PATCH v3 0/2] riscv: Use CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS to set misaligned access speed Charlie Jenkins
2024-02-02 23:54 ` Charlie Jenkins
2024-02-02 23:54 ` [PATCH v3 1/2] riscv: lib: Introduce has_fast_misaligned_access function Charlie Jenkins
2024-02-02 23:54 ` Charlie Jenkins
2024-02-14 14:24 ` Evan Green [this message]
2024-02-14 14:24 ` Evan Green
2024-02-02 23:54 ` [PATCH v3 2/2] riscv: Disable misaligned access probe when CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS Charlie Jenkins
2024-02-02 23:54 ` Charlie Jenkins
2024-02-14 14:24 ` Evan Green
2024-02-14 14:24 ` Evan Green
2024-02-16 19:24 ` Charlie Jenkins
2024-02-16 19:24 ` Charlie Jenkins
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=CALs-HsvLH_QYUViSBuBgF4vW_X4CJ3M8tgOVfAHi5WdVXx54fQ@mail.gmail.com \
--to=evan@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=charlie@rivosinc.com \
--cc=cleger@rivosinc.com \
--cc=ebiggers@kernel.org \
--cc=jszhang@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=quic_eberman@quicinc.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.