From: Charlie Jenkins <charlie@rivosinc.com>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Ard Biesheuvel <ardb@kernel.org>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: Add runtime constant support
Date: Mon, 27 Jan 2025 10:47:21 -0800 [thread overview]
Message-ID: <Z5fUudFfYz9FCh1k@ghost> (raw)
In-Reply-To: <dc193d9d-e8e5-4906-9fcd-ee8cc919acd7@codethink.co.uk>
On Mon, Jan 27, 2025 at 08:51:04AM +0000, Ben Dooks wrote:
> On 27/01/2025 08:18, Charlie Jenkins wrote:
> > Implement the runtime constant infrastructure for riscv. Use this
> > infrastructure to generate constants to be used by the d_hash()
> > function.
> >
> > This is the riscv variant of commit 94a2bc0f611c ("arm64: add 'runtime
> > constant' support") and commit e3c92e81711d ("runtime constants: add
> > x86 architecture support").
> >
> > Signed-off-by: Charlie Jenkins <charlie@rivosinc.com>
>
> I think my only comment on this is we should treat instructions as
> __le32 type and add the proper conversions when maniuplating them.
Fair enough, I will make the proper adjustements.
- Charlie
>
> --
> Ben Dooks http://www.codethink.co.uk/
> Senior Engineer Codethink - Providing Genius
>
> https://www.codethink.co.uk/privacy.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Charlie Jenkins <charlie@rivosinc.com>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Ard Biesheuvel <ardb@kernel.org>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: Add runtime constant support
Date: Mon, 27 Jan 2025 10:47:21 -0800 [thread overview]
Message-ID: <Z5fUudFfYz9FCh1k@ghost> (raw)
In-Reply-To: <dc193d9d-e8e5-4906-9fcd-ee8cc919acd7@codethink.co.uk>
On Mon, Jan 27, 2025 at 08:51:04AM +0000, Ben Dooks wrote:
> On 27/01/2025 08:18, Charlie Jenkins wrote:
> > Implement the runtime constant infrastructure for riscv. Use this
> > infrastructure to generate constants to be used by the d_hash()
> > function.
> >
> > This is the riscv variant of commit 94a2bc0f611c ("arm64: add 'runtime
> > constant' support") and commit e3c92e81711d ("runtime constants: add
> > x86 architecture support").
> >
> > Signed-off-by: Charlie Jenkins <charlie@rivosinc.com>
>
> I think my only comment on this is we should treat instructions as
> __le32 type and add the proper conversions when maniuplating them.
Fair enough, I will make the proper adjustements.
- Charlie
>
> --
> Ben Dooks http://www.codethink.co.uk/
> Senior Engineer Codethink - Providing Genius
>
> https://www.codethink.co.uk/privacy.html
next prev parent reply other threads:[~2025-01-27 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 8:18 [PATCH] riscv: Add runtime constant support Charlie Jenkins
2025-01-27 8:18 ` Charlie Jenkins
2025-01-27 8:51 ` Ben Dooks
2025-01-27 8:51 ` Ben Dooks
2025-01-27 18:47 ` Charlie Jenkins [this message]
2025-01-27 18:47 ` 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=Z5fUudFfYz9FCh1k@ghost \
--to=charlie@rivosinc.com \
--cc=ardb@kernel.org \
--cc=ben.dooks@codethink.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.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 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.