From: Mark Hatle <mark.hatle@kernel.crashing.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/6] ISA based RISC-V tune implementation
Date: Sun, 15 Jun 2025 21:29:19 -0500 [thread overview]
Message-ID: <1750040965-15015-1-git-send-email-mark.hatle@kernel.crashing.org> (raw)
From: Mark Hatle <mark.hatle@amd.com>
The following implements the risc-v processor tune based on the ISA approach
as documented in the oe-architecture post:
https://lists.openembedded.org/g/openembedded-architecture/message/2155
This set also attempts to make u-boot and kernel configurations dynamic
based on the TUNE_FEATURES.
For the linux-yocto, I suspect that the config fragments should be
sent to the kmeta (kernel-cache), but I'd like a review from Bruce and
others before I do this.
Additionally, this enables a new (optional) features_check for TUNE_FEATURES.
I've found numerous items in the system have certain RISC-V ISA expectations
that may need to be addressed over time, however the obvious one is the
Linux kernel requires ima_zicsr_zifencei. Since it has it's own -march=
setting this will ensure the processor defintion will be compatible.
Also dynamically configure the QEMU cpu based on the tune_features. This
is nice to ensure that what we're actually building should be able to run
on real hardware. However, it does highlight some of the (extension)
limitations in the current design. (limitations as in extension not yet
enabled.)
Note: OpenSBI _requires_ the 'c' extension or it will not execute. I
suspect this can be fixed, but it's beyond my capabilities at this time.
Mark Hatle (6):
riscv tunes: ISA Implementation of RISC-V tune features
linux-yocto: Enable risc-v TUNE_FEATURES ISA selections
u-boot: Dynamic RISC-V ISA configuration
qemuriscv: Dynamically configure qemu CPU
features_check.bbclass: Add support for required TUNE_FEATURES
linux-yocto.inc: State riscv required tune_features
meta/classes-recipe/features_check.bbclass | 2 +-
meta/conf/machine/include/riscv/README | 122 ++++++++++++++++
.../conf/machine/include/riscv/arch-riscv.inc | 138 +++++++++++++++++-
meta/conf/machine/include/riscv/qemuriscv.inc | 31 +++-
.../conf/machine/include/riscv/tune-riscv.inc | 40 ++---
meta/conf/machine/qemuriscv32.conf | 4 +-
meta/lib/oe/__init__.py | 2 +-
meta/lib/oe/tune.py | 81 ++++++++++
.../u-boot/files/u-boot-riscv-isa_a.cfg | 1 +
.../u-boot/files/u-boot-riscv-isa_c.cfg | 1 +
.../u-boot/files/u-boot-riscv-isa_clear.cfg | 6 +
.../u-boot/files/u-boot-riscv-isa_d.cfg | 1 +
.../u-boot/files/u-boot-riscv-isa_f.cfg | 1 +
.../u-boot/files/u-boot-riscv-isa_zbb.cfg | 1 +
.../u-boot/files/u-boot-riscv-isa_zicbom.cfg | 1 +
meta/recipes-bsp/u-boot/u-boot-common.inc | 12 ++
.../linux/files/risc-v-isa-c.cfg | 1 +
.../linux/files/risc-v-isa-clear.cfg | 9 ++
.../linux/files/risc-v-isa-fpu.cfg | 1 +
.../linux/files/risc-v-isa-rv32i.cfg | 2 +
.../linux/files/risc-v-isa-rv64i.cfg | 2 +
.../linux/files/risc-v-isa-v.cfg | 1 +
.../linux/files/risc-v-isa-zbb.cfg | 1 +
.../linux/files/risc-v-isa-zicbom.cfg | 1 +
meta/recipes-kernel/linux/linux-yocto.inc | 19 +++
25 files changed, 439 insertions(+), 42 deletions(-)
create mode 100644 meta/conf/machine/include/riscv/README
create mode 100644 meta/lib/oe/tune.py
create mode 100644 meta/recipes-bsp/u-boot/files/u-boot-riscv-isa_a.cfg
create mode 100644 meta/recipes-bsp/u-boot/files/u-boot-riscv-isa_c.cfg
create mode 100644 meta/recipes-bsp/u-boot/files/u-boot-riscv-isa_clear.cfg
create mode 100644 meta/recipes-bsp/u-boot/files/u-boot-riscv-isa_d.cfg
create mode 100644 meta/recipes-bsp/u-boot/files/u-boot-riscv-isa_f.cfg
create mode 100644 meta/recipes-bsp/u-boot/files/u-boot-riscv-isa_zbb.cfg
create mode 100644 meta/recipes-bsp/u-boot/files/u-boot-riscv-isa_zicbom.cfg
create mode 100644 meta/recipes-kernel/linux/files/risc-v-isa-c.cfg
create mode 100644 meta/recipes-kernel/linux/files/risc-v-isa-clear.cfg
create mode 100644 meta/recipes-kernel/linux/files/risc-v-isa-fpu.cfg
create mode 100644 meta/recipes-kernel/linux/files/risc-v-isa-rv32i.cfg
create mode 100644 meta/recipes-kernel/linux/files/risc-v-isa-rv64i.cfg
create mode 100644 meta/recipes-kernel/linux/files/risc-v-isa-v.cfg
create mode 100644 meta/recipes-kernel/linux/files/risc-v-isa-zbb.cfg
create mode 100644 meta/recipes-kernel/linux/files/risc-v-isa-zicbom.cfg
--
2.34.1
next reply other threads:[~2025-06-16 2:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 2:29 Mark Hatle [this message]
2025-06-16 2:29 ` [PATCH 1/6] riscv tunes: ISA Implementation of RISC-V tune features Mark Hatle
2025-06-16 10:11 ` [OE-core] " Richard Purdie
2025-06-16 14:21 ` Mark Hatle
2025-06-16 2:29 ` [PATCH 2/6] linux-yocto: Enable risc-v TUNE_FEATURES ISA selections Mark Hatle
2025-06-16 10:50 ` Bruce Ashfield
2025-06-16 2:29 ` [PATCH 3/6] u-boot: Dynamic RISC-V ISA configuration Mark Hatle
2025-06-16 2:29 ` [PATCH 4/6] qemuriscv: Dynamically configure qemu CPU Mark Hatle
2025-06-16 2:29 ` [PATCH 5/6] features_check.bbclass: Add support for required TUNE_FEATURES Mark Hatle
2025-06-16 2:29 ` [PATCH 6/6] linux-yocto.inc: State riscv required tune_features Mark Hatle
2025-06-16 11:05 ` [OE-core] " Bruce Ashfield
2025-06-16 14:07 ` Mark Hatle
2025-06-16 10:11 ` [OE-core] [PATCH 0/6] ISA based RISC-V tune implementation Gyorgy Sarvari
2025-06-16 14:12 ` Mark Hatle
[not found] ` <18498B713347A8EF.22186@lists.openembedded.org>
2025-06-16 16:00 ` Mark Hatle
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=1750040965-15015-1-git-send-email-mark.hatle@kernel.crashing.org \
--to=mark.hatle@kernel.crashing.org \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox