qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ran Wang <wangran@bosc.ac.cn>
To: Alistair Francis <alistair23@gmail.com>,
	Huang Borong <3543977024@qq.com>
Cc: qemu-riscv@nongnu.org, palmer@dabbelt.com,
	alistair.francis@wdc.com, liwei1518@gmail.com,
	dbarboza@ventanamicro.com, zhiwei_liu@linux.alibaba.com,
	qemu-devel@nongnu.org
Subject: Re: [PATCH v3 1/2] target/riscv: Add BOSC's Xiangshan Kunminghu CPU
Date: Fri, 25 Apr 2025 15:01:42 +0800	[thread overview]
Message-ID: <f39a07eb-e63d-4373-ab7a-fd83fab37c68@bosc.ac.cn> (raw)
In-Reply-To: <CAKmqyKOwbLJrRTkVrGO8+Kd-5SAEj1GU7ToytB8b66b_gbADHg@mail.gmail.com>

Hi Alistair

On 2025/4/24 18:49, Alistair Francis wrote:
> On Tue, Apr 8, 2025 at 12:23 PM Huang Borong <huangborong@bosc.ac.cn> wrote:
>>
>> Add a CPU entry for the Xiangshan Kunminghu CPU, an open-source,
>> high-performance RISC-V processor. More details can be found at:

<snip>

>> +    cpu->cfg.ext_ssaia = true;
>> +
>> +    /* RVA23 Profiles */
>> +    cpu->cfg.ext_zicbom = true;
>> +    cpu->cfg.ext_zicbop = true;
>> +    cpu->cfg.ext_zicboz = true;
>> +    cpu->cfg.ext_svade = true;
>> +
>> +#ifndef CONFIG_USER_ONLY
>> +    set_satp_mode_max_supported(cpu, VM_1_10_SV48);
>> +#endif
>> +}
>> +
> 
> Sorry about this, but we just merged a new way of defining CPU types.
> Can you please rebase on
> https://github.com/alistair23/qemu/tree/riscv-to-apply.next to use the
> new macros? It shouldn't be much work, just a little restructuring.
> 
> When sending a new version can you also include a cover letter [1]
> 
> 1: https://www.qemu.org/docs/master/devel/submitting-a-patch.html#include-a-meaningful-cover-letter

Sure, Borong just left BOSC and I will take over his job and send out 
next version patch mail later.

Thanks & Regards,

Ran

> Alistair
> 
>>   #ifdef CONFIG_TCG
>>   static void rv128_base_cpu_init(Object *obj)
>>   {
>> @@ -3261,6 +3331,8 @@ static const TypeInfo riscv_cpu_type_infos[] = {
>>       DEFINE_VENDOR_CPU(TYPE_RISCV_CPU_VEYRON_V1,  MXL_RV64,  rv64_veyron_v1_cpu_init),
>>       DEFINE_VENDOR_CPU(TYPE_RISCV_CPU_XIANGSHAN_NANHU,
>>                                                    MXL_RV64, rv64_xiangshan_nanhu_cpu_init),
>> +    DEFINE_VENDOR_CPU(TYPE_RISCV_CPU_XIANGSHAN_KMH,
>> +                                                 MXL_RV64,  rv64_xiangshan_kmh_cpu_init),
>>   #ifdef CONFIG_TCG
>>       DEFINE_DYNAMIC_CPU(TYPE_RISCV_CPU_BASE128,   MXL_RV128, rv128_base_cpu_init),
>>   #endif /* CONFIG_TCG */
>> --
>> 2.34.1
>>
>>



      reply	other threads:[~2025-04-25 11:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08  2:21 [PATCH v3 1/2] target/riscv: Add BOSC's Xiangshan Kunminghu CPU Huang Borong
2025-04-08 12:47 ` Daniel Henrique Barboza
2025-04-24 10:49 ` Alistair Francis
2025-04-25  7:01   ` Ran Wang [this message]

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=f39a07eb-e63d-4373-ab7a-fd83fab37c68@bosc.ac.cn \
    --to=wangran@bosc.ac.cn \
    --cc=3543977024@qq.com \
    --cc=alistair.francis@wdc.com \
    --cc=alistair23@gmail.com \
    --cc=dbarboza@ventanamicro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).