All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Henrique Barboza <daniel.barboza@oss.qualcomm.com>
To: qemu-devel@nongnu.org
Cc: qemu-riscv@nongnu.org, alistair.francis@wdc.com,
	liwei1518@gmail.com, zhiwei_liu@linux.alibaba.com,
	chao.liu@processmission.com, andrew.jones@oss.qualcomm.com,
	leif.lindholm@oss.qualcomm.com,
	Daniel Henrique Barboza <daniel.barboza@oss.qualcomm.com>,
	Palmer Dabbelt <palmer@dabbelt.com>
Subject: [PATCH v10 1/5] target/riscv/cpu.c: remove 'bare' condition for .profile
Date: Fri,  4 Sep 2026 16:56:06 -0300	[thread overview]
Message-ID: <20260904195610.964829-2-daniel.barboza@oss.qualcomm.com> (raw)
In-Reply-To: <20260904195610.964829-1-daniel.barboza@oss.qualcomm.com>

We want to configure other CPU types to use profiles as an alternative
to adding every profile extension explicitly, i.e. a profile is nothing
more than an extension bundle.

This means that a vendor CPU can set .profile=rva23s64 while having the
same handling as any other vendor CPU. Same thing with all other CPU
types.

Signed-off-by: Daniel Henrique Barboza <daniel.barboza@oss.qualcomm.com>
Reviewed-by: Andrew Jones <andrew.jones@oss.qualcomm.com>
Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
Reviewed-by: Chao Liu <chao.liu@processmission.com>
---
 target/riscv/cpu.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/target/riscv/cpu.c b/target/riscv/cpu.c
index 652311ddef..185474a8cf 100644
--- a/target/riscv/cpu.c
+++ b/target/riscv/cpu.c
@@ -3096,7 +3096,6 @@ static void riscv_cpu_class_base_init(ObjectClass *c, const void *data)
         mcc->def->bare |= def->bare;
         if (def->profile) {
             assert(profile_extends(def->profile, mcc->def->profile));
-            assert(mcc->def->bare);
             mcc->def->profile = def->profile;
         }
         if (def->misa_mxl_max) {
-- 
2.43.0



  reply	other threads:[~2026-09-04 19:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 19:56 [PATCH v10 0/5] hw/riscv: Server Platform Reference Board Daniel Henrique Barboza
2026-09-04 19:56 ` Daniel Henrique Barboza [this message]
2026-09-08  3:26   ` [PATCH v10 1/5] target/riscv/cpu.c: remove 'bare' condition for .profile Sunil V L
2026-09-04 19:56 ` [PATCH v10 2/5] target/riscv: add riscv-server-ref CPU Daniel Henrique Barboza
2026-09-08  7:30   ` Sunil V L
2026-09-08  9:08   ` Andrew Jones
2026-09-08 18:40     ` Daniel Henrique Barboza
2026-09-04 19:56 ` [PATCH v10 3/5] hw/riscv: server platform reference machine Daniel Henrique Barboza
2026-09-08  3:25   ` Sunil V L
2026-09-08 10:40   ` Andrew Jones
2026-09-08 18:44     ` Daniel Henrique Barboza
2026-09-04 19:56 ` [PATCH v10 4/5] tests/functional/riscv64: add riscv-server-ref tests Daniel Henrique Barboza
2026-09-08  7:34   ` Sunil V L
2026-09-08  9:11   ` Andrew Jones
2026-09-08 10:17     ` Andrew Jones
2026-09-04 19:56 ` [PATCH v10 5/5] docs: add riscv-server-ref.rst Daniel Henrique Barboza
2026-09-08  7:32   ` Sunil V L
2026-09-08 10:05   ` Andrew Jones
2026-09-08 18:50     ` Daniel Henrique Barboza

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=20260904195610.964829-2-daniel.barboza@oss.qualcomm.com \
    --to=daniel.barboza@oss.qualcomm.com \
    --cc=alistair.francis@wdc.com \
    --cc=andrew.jones@oss.qualcomm.com \
    --cc=chao.liu@processmission.com \
    --cc=leif.lindholm@oss.qualcomm.com \
    --cc=liwei1518@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=zhiwei_liu@linux.alibaba.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.