From: schspa <schspa@gmail.com>
To: qemu-devel@nongnu.org
Subject: [PATCH] arm: xlnx-versal: fix virtio-mmio base address assignment
Date: Thu, 04 Feb 2021 14:58:49 +0800 [thread overview]
Message-ID: <3362132240927a23ecca7b9d8cfd6e4130509eea.camel@gmail.com> (raw)
At the moment the following QEMU command line triggers an assertion
failure On xlnx-versal SOC:
qemu-system-aarch64 \
-machine xlnx-versal-virt -nographic -smp 2 -m 128 \
-fsdev local,id=shareid,path=${HOME}/work,security_model=none \
-device virtio-9p-device,fsdev=shareid,mount_tag=share \
-fsdev local,id=shareid1,path=${HOME}/Music,security_model=none \
-device virtio-9p-device,fsdev=shareid1,mount_tag=share1
qemu-system-aarch64: ../migration/savevm.c:860:
vmstate_register_with_alias_id:
Assertion `!se->compat || se->instance_id == 0' failed.
This problem was fixed on arm virt platform in patch
https://lists.nongnu.org/archive/html/qemu-devel/2016-07/msg01119.html
It works perfectly on arm virt platform. but there is still there on
xlnx-versal SOC.
The main difference between arm virt and xlnx-versal is they use
different way to create virtio-mmio qdev. on arm virt, it calls
sysbus_create_simple("virtio-mmio", base, pic[irq]); which will call
sysbus_mmio_map internally and assign base address to subsys device
mmio correctly. but xlnx-versal's implements won't do this.
However, xlnx-versal can't switch to sysbus_create_simple() to create
virtio-mmio device. It's because xlnx-versal's cpu use
VersalVirt.soc.fpd.apu.mr as it's memory. which is subregion of
system_memory. sysbus_create_simple will add virtio to system_memory,
which can't be accessed by cpu.
We can solve this by simply assign mmio[0].addr directly. makes
virtio_mmio_bus_get_dev_path to produce correct unique device path.
Signed-off-by: schspa <schspa@gmail.com>
---
hw/arm/xlnx-versal-virt.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/arm/xlnx-versal-virt.c b/hw/arm/xlnx-versal-virt.c
index 8482cd6196..87b92ec6c3 100644
--- a/hw/arm/xlnx-versal-virt.c
+++ b/hw/arm/xlnx-versal-virt.c
@@ -490,6 +490,7 @@ static void create_virtio_regions(VersalVirt *s)
object_property_add_child(OBJECT(&s->soc), name, OBJECT(dev));
sysbus_realize_and_unref(SYS_BUS_DEVICE(dev), &error_fatal);
sysbus_connect_irq(SYS_BUS_DEVICE(dev), 0, pic_irq);
+ SYS_BUS_DEVICE(dev)->mmio[0].addr = base;
mr = sysbus_mmio_get_region(SYS_BUS_DEVICE(dev), 0);
memory_region_add_subregion(&s->soc.mr_ps, base, mr);
g_free(name);
--
2.30.0
next reply other threads:[~2021-02-04 7:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 6:58 schspa [this message]
2021-02-04 8:19 ` [PATCH] arm: xlnx-versal: fix virtio-mmio base address assignment Philippe Mathieu-Daudé
2021-02-04 9:04 ` schspa
2021-02-05 7:53 ` Philippe Mathieu-Daudé
2021-02-05 10:03 ` Peter Maydell
2021-02-05 10:31 ` Philippe Mathieu-Daudé
2021-02-05 11:18 ` Peter Maydell
2021-02-05 14:08 ` Edgar E. Iglesias
2021-02-08 5:34 ` schspa
2021-02-08 11:57 ` Laszlo Ersek
2021-02-08 12:59 ` Peter Maydell
2021-02-25 5:36 ` [PATCH v4] virtio-mmio: improve virtio-mmio get_dev_path alog schspa
2021-03-05 11:57 ` Peter Maydell
2021-03-06 2:28 ` Shi Schspa
2021-02-25 6:35 ` [PATCH] arm: xlnx-versal: fix virtio-mmio base address assignment schspa
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=3362132240927a23ecca7b9d8cfd6e4130509eea.camel@gmail.com \
--to=schspa@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).