All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jones <ajones@ventanamicro.com>
To: Conor Dooley <conor.dooley@microchip.com>
Cc: linux-riscv@lists.infradead.org, aou@eecs.berkeley.edu,
	conor@kernel.org, devicetree@vger.kernel.org, guoren@kernel.org,
	heiko@sntech.de, krzysztof.kozlowski+dt@linaro.org,
	linux-kernel@vger.kernel.org, palmer@dabbelt.com,
	paul.walmsley@sifive.com, robh+dt@kernel.org
Subject: Re: [RFC 0/2] Putting some basic order on isa extension stuff
Date: Tue, 29 Nov 2022 16:48:32 +0100	[thread overview]
Message-ID: <20221129154832.27or3ywsx7npuqzq@kamzik> (raw)
In-Reply-To: <20221129144742.2935581-1-conor.dooley@microchip.com>

On Tue, Nov 29, 2022 at 02:47:41PM +0000, Conor Dooley wrote:
> RFC:
> - I have not even tested this, I just did an allmodconfig
> - I don't know if I re-ordered something that is sacrosanct
> - I don't know if I changed all of the instances
> - I didn't write a proper commit message for "patch" 2/2
> 
> With those caveats out of the way - all I did here was try to make
> things consistent so that it'd be easier to point patch submitters at a
> "do this order please".
> 
> I never know which of these can be moved without breaking stuff - but
> they all seem to be internal use stuff since they're not in uapi?
> 
> @drew, I didn't touch the KVM ones - are they re-sortable too? My base
> here is rc7 so if you did a reorder at any point there I'd not see it ;)

Right, we can't touch enum KVM_RISCV_ISA_EXT_ID as that's UAPI. All new
extensions must be added at the bottom. We originally also had to keep
kvm_isa_ext_arr[] in that order, but commit 1b5cbb8733f9 ("RISC-V: KVM:
Make ISA ext mappings explicit") allows us to list its elements in any
order, which means we could sort them in canonical order, if we wanted
to. I think I'd rather have them in alphabetical order, though (they
nearly are at the moment, except for the bottom two...) The only other
place we have ISA extensions listed in KVM is in a switch statement,
which of course doesn't matter, and it's currently in alphabetical order.

Thanks,
drew

_______________________________________________
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: Andrew Jones <ajones@ventanamicro.com>
To: Conor Dooley <conor.dooley@microchip.com>
Cc: linux-riscv@lists.infradead.org, aou@eecs.berkeley.edu,
	conor@kernel.org, devicetree@vger.kernel.org, guoren@kernel.org,
	heiko@sntech.de, krzysztof.kozlowski+dt@linaro.org,
	linux-kernel@vger.kernel.org, palmer@dabbelt.com,
	paul.walmsley@sifive.com, robh+dt@kernel.org
Subject: Re: [RFC 0/2] Putting some basic order on isa extension stuff
Date: Tue, 29 Nov 2022 16:48:32 +0100	[thread overview]
Message-ID: <20221129154832.27or3ywsx7npuqzq@kamzik> (raw)
In-Reply-To: <20221129144742.2935581-1-conor.dooley@microchip.com>

On Tue, Nov 29, 2022 at 02:47:41PM +0000, Conor Dooley wrote:
> RFC:
> - I have not even tested this, I just did an allmodconfig
> - I don't know if I re-ordered something that is sacrosanct
> - I don't know if I changed all of the instances
> - I didn't write a proper commit message for "patch" 2/2
> 
> With those caveats out of the way - all I did here was try to make
> things consistent so that it'd be easier to point patch submitters at a
> "do this order please".
> 
> I never know which of these can be moved without breaking stuff - but
> they all seem to be internal use stuff since they're not in uapi?
> 
> @drew, I didn't touch the KVM ones - are they re-sortable too? My base
> here is rc7 so if you did a reorder at any point there I'd not see it ;)

Right, we can't touch enum KVM_RISCV_ISA_EXT_ID as that's UAPI. All new
extensions must be added at the bottom. We originally also had to keep
kvm_isa_ext_arr[] in that order, but commit 1b5cbb8733f9 ("RISC-V: KVM:
Make ISA ext mappings explicit") allows us to list its elements in any
order, which means we could sort them in canonical order, if we wanted
to. I think I'd rather have them in alphabetical order, though (they
nearly are at the moment, except for the bottom two...) The only other
place we have ISA extensions listed in KVM is in a switch statement,
which of course doesn't matter, and it's currently in alphabetical order.

Thanks,
drew

  reply	other threads:[~2022-11-29 15:48 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24 13:04 [PATCH 0/2] riscv,isa fixups Conor Dooley
2022-11-24 13:04 ` Conor Dooley
2022-11-24 13:04 ` [PATCH 1/2] dt-bindings: riscv: fix underscore requirement for addtional standard extensions Conor Dooley
2022-11-24 13:04   ` Conor Dooley
2022-11-25  1:12   ` Guo Ren
2022-11-25  1:12     ` Guo Ren
2022-11-24 13:04 ` [PATCH 2/2] dt-bindings: riscv: fix single letter canonical order Conor Dooley
2022-11-24 13:04   ` Conor Dooley
2022-11-24 13:42   ` Heiko Stübner
2022-11-24 13:42     ` Heiko Stübner
2022-11-24 13:52     ` Conor Dooley
2022-11-24 13:52       ` Conor Dooley
2022-11-28 17:41     ` Palmer Dabbelt
2022-11-28 17:41       ` Palmer Dabbelt
2022-11-28 18:08       ` Conor Dooley
2022-11-28 18:08         ` Conor Dooley
2022-11-28 18:12         ` Palmer Dabbelt
2022-11-28 18:12           ` Palmer Dabbelt
2022-11-28 19:17           ` Conor Dooley
2022-11-28 19:17             ` Conor Dooley
2022-11-28 23:41             ` Palmer Dabbelt
2022-11-28 23:41               ` Palmer Dabbelt
2022-11-29  5:19               ` Andrew Jones
2022-11-29  5:19                 ` Andrew Jones
2022-11-29 11:40                 ` Conor Dooley
2022-11-29 11:40                   ` Conor Dooley
2022-11-29 14:47                   ` [RFC 0/2] Putting some basic order on isa extension stuff Conor Dooley
2022-11-29 14:47                     ` Conor Dooley
2022-11-29 15:48                     ` Andrew Jones [this message]
2022-11-29 15:48                       ` Andrew Jones
2022-11-29 16:50                       ` Conor Dooley
2022-11-29 16:50                         ` Conor Dooley
2022-11-29 14:47                   ` [RFC 1/2] RISC-V: clarify ISA string ordering rules in cpu.c Conor Dooley
2022-11-29 14:47                     ` Conor Dooley
2022-11-29 16:12                     ` Andrew Jones
2022-11-29 16:12                       ` Andrew Jones
2022-11-29 16:54                       ` Conor Dooley
2022-11-29 16:54                         ` Conor Dooley
2022-11-29 17:19                         ` Andrew Jones
2022-11-29 17:19                           ` Andrew Jones
2022-11-29 17:48                           ` Conor Dooley
2022-11-29 17:48                             ` Conor Dooley
2022-11-29 14:47                   ` [RFC 2/2] RISC-V: resort all extensions in "canonical" order Conor Dooley
2022-11-29 14:47                     ` Conor Dooley
2022-11-29 16:35                     ` Andrew Jones
2022-11-29 16:35                       ` Andrew Jones
2022-12-01 13:51                   ` [PATCH] Documentation: riscv: note that counter access is part of the uABI Conor Dooley
2022-12-01 13:51                     ` Conor Dooley
2022-12-01 19:21                     ` Palmer Dabbelt
2022-12-01 19:21                       ` Palmer Dabbelt
2022-12-03 10:38                       ` Jonathan Corbet
2022-12-03 10:38                         ` Jonathan Corbet
2022-12-03 10:45                         ` Jonathan Corbet
2022-12-03 10:45                           ` Jonathan Corbet
2022-12-03 10:56                           ` Conor Dooley
2022-12-03 10:56                             ` Conor Dooley
2023-01-09 21:36                             ` Atish Patra
2023-01-09 21:36                               ` Atish Patra
2023-01-09 21:46                               ` Conor Dooley
2023-01-09 21:46                                 ` Conor Dooley
2022-11-25  1:13   ` [PATCH 2/2] dt-bindings: riscv: fix single letter canonical order Guo Ren
2022-11-25  1:13     ` Guo Ren

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=20221129154832.27or3ywsx7npuqzq@kamzik \
    --to=ajones@ventanamicro.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=guoren@kernel.org \
    --cc=heiko@sntech.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh+dt@kernel.org \
    /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.