From: Conor Dooley <conor@kernel.org>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: Sunil V L <sunilvl@ventanamicro.com>,
linux-riscv@lists.infradead.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] RISC-V: Don't include Zicsr or Zifencei in I from ACPI
Date: Wed, 12 Jul 2023 18:13:38 +0100 [thread overview]
Message-ID: <20230712-quickness-viscosity-ca1a15ccdfcb@spud> (raw)
In-Reply-To: <mhng-c30cb4e2-0574-4051-b220-01601d9579de@palmer-ri-x1c9a>
[-- Attachment #1: Type: text/plain, Size: 789 bytes --]
On Wed, Jul 12, 2023 at 10:05:39AM -0700, Palmer Dabbelt wrote:
> On Tue, 11 Jul 2023 15:52:56 PDT (-0700), Conor Dooley wrote:
> > Although my rationale was that if we get as far as here, then Zicsr and
> > Zifencei are going to be enabled anyway so there is no harm in setting
> > it for both. I probably should have been less of a cute hoor though.
> > Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
>
> I think there's no way to get here without the extensions, not 100% sure
> though. I'm mainly trying to avoid going down the same rabbit hole of ISA
> string compatibility hacks in ACPI that we have for DT, though -- I'm sure
> we'll end up with a mess as soon as we release, but might as well catch as
> much as we can.
Seems reasonable to me chief :+1:
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: linux-acpi@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [PATCH] RISC-V: Don't include Zicsr or Zifencei in I from ACPI
Date: Wed, 12 Jul 2023 18:13:38 +0100 [thread overview]
Message-ID: <20230712-quickness-viscosity-ca1a15ccdfcb@spud> (raw)
In-Reply-To: <mhng-c30cb4e2-0574-4051-b220-01601d9579de@palmer-ri-x1c9a>
[-- Attachment #1.1: Type: text/plain, Size: 789 bytes --]
On Wed, Jul 12, 2023 at 10:05:39AM -0700, Palmer Dabbelt wrote:
> On Tue, 11 Jul 2023 15:52:56 PDT (-0700), Conor Dooley wrote:
> > Although my rationale was that if we get as far as here, then Zicsr and
> > Zifencei are going to be enabled anyway so there is no harm in setting
> > it for both. I probably should have been less of a cute hoor though.
> > Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
>
> I think there's no way to get here without the extensions, not 100% sure
> though. I'm mainly trying to avoid going down the same rabbit hole of ISA
> string compatibility hacks in ACPI that we have for DT, though -- I'm sure
> we'll end up with a mess as soon as we release, but might as well catch as
> much as we can.
Seems reasonable to me chief :+1:
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-07-12 17:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 22:46 [PATCH] RISC-V: Don't include Zicsr or Zifencei in I from ACPI Palmer Dabbelt
2023-07-11 22:46 ` Palmer Dabbelt
2023-07-11 22:52 ` Conor Dooley
2023-07-11 22:52 ` Conor Dooley
2023-07-12 17:05 ` Palmer Dabbelt
2023-07-12 17:05 ` Palmer Dabbelt
2023-07-12 17:13 ` Conor Dooley [this message]
2023-07-12 17:13 ` Conor Dooley
2023-07-12 6:42 ` Sunil V L
2023-07-12 6:42 ` Sunil V L
2023-07-13 23:50 ` patchwork-bot+linux-riscv
2023-07-13 23:50 ` patchwork-bot+linux-riscv
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=20230712-quickness-viscosity-ca1a15ccdfcb@spud \
--to=conor@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@rivosinc.com \
--cc=sunilvl@ventanamicro.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.