All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Alistair Francis <alistair23@gmail.com>,
	Sai Pavan Boddu <sai.pavan.boddu@amd.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
	Paolo Bonzini <pbonzini@redhat.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Alistair Francis <alistair.francis@wdc.com>,
	Bin Meng <bmeng.cn@gmail.com>, Weiwei Li <liwei1518@gmail.com>,
	Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
	Liu Zhiwei <zhiwei_liu@linux.alibaba.com>
Subject: Re: [PATCH v2] hw/riscv: Add Microblaze V 32bit virt board
Date: Wed, 30 Oct 2024 06:53:47 +0100	[thread overview]
Message-ID: <7dbcb2de-89f9-445b-a096-2a3d03a2dfe7@amd.com> (raw)
In-Reply-To: <CAKmqyKNfoakaJ66PCN49x5+=gVkAnQVV1UWTdPe7ARr3RA8ouA@mail.gmail.com>

Hi Alistair,

On 10/30/24 03:54, Alistair Francis wrote:
> On Thu, Oct 17, 2024 at 5:26 PM Sai Pavan Boddu <sai.pavan.boddu@amd.com> wrote:

>> diff --git a/hw/riscv/microblaze-v-virt.c b/hw/riscv/microblaze-v-virt.c
>> new file mode 100644
>> index 00000000000..6603e6d6b06
>> --- /dev/null
>> +++ b/hw/riscv/microblaze-v-virt.c
>> @@ -0,0 +1,181 @@
>> +/*
>> + * QEMU model of Microblaze V (32bit version)
>> + *
>> + * based on hw/microblaze/petalogix_ml605_mmu.c
> 
> Just a question, are you sure the virt board should be based on the
> petalogix_ml605_mmu?

It is definitely based on ml605 and it is fair to say it and keep origin 
copyrights around.

> This will be the reference Microblaze V implementation in QEMU, and
> the petalogix_ml605_mmu might be a bit old now. It also uses a lot of
> the Microblaze architecture components (like the interrupt controller)
> compared to the RISC-V architecture components which might cause
> issues for you in the future.
> 
> Just something to keep in mind

And the reason is that it is really design like that in design tool (Vivado).
There is no risc-v specific interrupt controller use but origin axi intc used in 
origin Microblaze designs. Timer is the same story.

ml605 board and it's chip is old but IPs which are used are still supported and 
used in new designs.

And regarding using virt in name. We can create design like it is described but 
it is not going to work on standard evaluation boards without extra fmc cards 
for example.
It means word virt is just description that it is not really target any specific 
board. Definitely name can change and suggestions are welcome.

Thanks,
Michal





  reply	other threads:[~2024-10-30 13:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17  7:25 [PATCH v2] hw/riscv: Add Microblaze V 32bit virt board Sai Pavan Boddu
2024-10-29 15:44 ` Francisco Iglesias
2024-10-30  2:54 ` Alistair Francis
2024-10-30  5:53   ` Michal Simek [this message]
2024-10-31  4:06     ` Philippe Mathieu-Daudé
2024-10-31  4:31       ` Alistair Francis
2024-11-04 17:37         ` Boddu, Sai Pavan
2024-10-31  8:43       ` Michal Simek
2024-10-31 15:59         ` Philippe Mathieu-Daudé
2024-11-04 17:39           ` Boddu, Sai Pavan

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=7dbcb2de-89f9-445b-a096-2a3d03a2dfe7@amd.com \
    --to=michal.simek@amd.com \
    --cc=alistair.francis@wdc.com \
    --cc=alistair23@gmail.com \
    --cc=bmeng.cn@gmail.com \
    --cc=dbarboza@ventanamicro.com \
    --cc=liwei1518@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=sai.pavan.boddu@amd.com \
    --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.