From: "Heiko Stübner" <heiko@sntech.de>
To: Palmer Dabbelt <palmer@rivosinc.com>, Evan Green <evan@rivosinc.com>
Cc: Anup Patel <apatel@ventanamicro.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Atish Patra <atishp@rivosinc.com>,
Randy Dunlap <rdunlap@infradead.org>,
vineetg@rivosinc.com, linux-kernel@vger.kernel.org,
Conor Dooley <conor@kernel.org>,
Conor Dooley <conor.dooley@microchip.com>,
Evan Green <evan@rivosinc.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
slewis@rivosinc.com, Paul Walmsley <paul.walmsley@sifive.com>,
Mayuresh Chitale <mchitale@ventanamicro.com>,
Dao Lu <daolu@rivosinc.com>,
linux-riscv@lists.infradead.org,
Andrew Jones <ajones@ventanamicro.com>
Subject: Re: [PATCH v4 1/6] RISC-V: Move struct riscv_cpuinfo to new header
Date: Tue, 21 Mar 2023 21:22:51 +0100 [thread overview]
Message-ID: <3703783.44csPzL39Z@diego> (raw)
In-Reply-To: <20230314183220.513101-2-evan@rivosinc.com>
Am Dienstag, 14. März 2023, 19:32:15 CET schrieb Evan Green:
> In preparation for tracking and exposing microarchitectural details to
> userspace (like whether or not unaligned accesses are fast), move the
> riscv_cpuinfo struct out to its own new cpufeatures.h header. It will
> need to be used by more than just cpu.c.
>
> Signed-off-by: Evan Green <evan@rivosinc.com>
> Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
Reviewed-by: Heiko Stuebner <heiko.stuebner@vrull.eu>
_______________________________________________
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: "Heiko Stübner" <heiko@sntech.de>
To: Palmer Dabbelt <palmer@rivosinc.com>, Evan Green <evan@rivosinc.com>
Cc: slewis@rivosinc.com, Conor Dooley <conor@kernel.org>,
vineetg@rivosinc.com, Evan Green <evan@rivosinc.com>,
Conor Dooley <conor.dooley@microchip.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Andrew Jones <ajones@ventanamicro.com>,
Anup Patel <apatel@ventanamicro.com>,
Atish Patra <atishp@rivosinc.com>, Dao Lu <daolu@rivosinc.com>,
Mayuresh Chitale <mchitale@ventanamicro.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Randy Dunlap <rdunlap@infradead.org>,
Sunil V L <sunilvl@ventanamicro.com>,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [PATCH v4 1/6] RISC-V: Move struct riscv_cpuinfo to new header
Date: Tue, 21 Mar 2023 21:22:51 +0100 [thread overview]
Message-ID: <3703783.44csPzL39Z@diego> (raw)
In-Reply-To: <20230314183220.513101-2-evan@rivosinc.com>
Am Dienstag, 14. März 2023, 19:32:15 CET schrieb Evan Green:
> In preparation for tracking and exposing microarchitectural details to
> userspace (like whether or not unaligned accesses are fast), move the
> riscv_cpuinfo struct out to its own new cpufeatures.h header. It will
> need to be used by more than just cpu.c.
>
> Signed-off-by: Evan Green <evan@rivosinc.com>
> Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
Reviewed-by: Heiko Stuebner <heiko.stuebner@vrull.eu>
next prev parent reply other threads:[~2023-03-21 20:23 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 18:32 [PATCH v4 0/6] RISC-V Hardware Probing User Interface Evan Green
2023-03-14 18:32 ` [PATCH v4 1/6] RISC-V: Move struct riscv_cpuinfo to new header Evan Green
2023-03-14 18:32 ` Evan Green
2023-03-21 20:22 ` Heiko Stübner [this message]
2023-03-21 20:22 ` Heiko Stübner
2023-03-14 18:32 ` [PATCH v4 2/6] RISC-V: Add a syscall for HW probing Evan Green
2023-03-14 18:32 ` Evan Green
2023-03-21 20:23 ` Heiko Stübner
2023-03-21 20:23 ` Heiko Stübner
2023-03-14 18:32 ` [PATCH v4 3/6] RISC-V: hwprobe: Add support for RISCV_HWPROBE_BASE_BEHAVIOR_IMA Evan Green
2023-03-14 18:32 ` Evan Green
2023-03-21 16:41 ` Heiko Stübner
2023-03-21 16:41 ` Heiko Stübner
2023-03-22 16:17 ` Evan Green
2023-03-22 16:17 ` Evan Green
2023-03-21 20:25 ` Heiko Stübner
2023-03-21 20:25 ` Heiko Stübner
2023-03-22 15:35 ` Conor Dooley
2023-03-22 15:35 ` Conor Dooley
2023-03-22 16:04 ` Evan Green
2023-03-22 16:04 ` Evan Green
2023-03-14 18:32 ` [PATCH v4 4/6] RISC-V: hwprobe: Support probing of misaligned access performance Evan Green
2023-03-14 18:32 ` Evan Green
2023-03-17 10:08 ` Heiko Stübner
2023-03-17 10:08 ` Heiko Stübner
2023-03-21 15:35 ` Evan Green
2023-03-21 15:35 ` Evan Green
2023-03-18 12:02 ` Conor Dooley
2023-03-18 12:02 ` Conor Dooley
2023-03-21 20:27 ` Heiko Stübner
2023-03-21 20:27 ` Heiko Stübner
2023-03-14 18:32 ` [PATCH v4 5/6] selftests: Test the new RISC-V hwprobe interface Evan Green
2023-03-14 18:32 ` Evan Green
2023-03-14 18:32 ` [PATCH v4 6/6] RISC-V: Add hwprobe vDSO function and data Evan Green
2023-03-14 18:32 ` Evan Green
2023-03-17 11:08 ` kernel test robot
2023-03-17 11:08 ` kernel test robot
2023-03-17 12:10 ` kernel test robot
2023-03-17 12:10 ` kernel test robot
2023-03-21 20:32 ` [PATCH v4 0/6] RISC-V Hardware Probing User Interface Heiko Stübner
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=3703783.44csPzL39Z@diego \
--to=heiko@sntech.de \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=atishp@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=daolu@rivosinc.com \
--cc=evan@rivosinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mchitale@ventanamicro.com \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=rdunlap@infradead.org \
--cc=slewis@rivosinc.com \
--cc=vineetg@rivosinc.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.