From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [PATCH v2 2/2] system: Enable the device aliases for or1k, too
Date: Fri, 5 Jul 2024 14:45:28 +0200 [thread overview]
Message-ID: <20240705124528.97471-3-philmd@linaro.org> (raw)
In-Reply-To: <20240705124528.97471-1-philmd@linaro.org>
From: Thomas Huth <thuth@redhat.com>
Now that we've got a "virt" machine for or1k that supports PCI
too (commit 40fef82c4e "hw/openrisc: Add PCI bus support to virt")
we can also enable the virtio device aliases like we do on other
similar platforms. This will e.g. help to run the iotests with
qemu-system-or1k later.
Signed-off-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Message-ID: <20240705090808.1305765-1-thuth@redhat.com>
Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
---
system/qdev-monitor.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/system/qdev-monitor.c b/system/qdev-monitor.c
index acdc8b73a3..44994ea0e1 100644
--- a/system/qdev-monitor.c
+++ b/system/qdev-monitor.c
@@ -61,6 +61,7 @@ typedef struct QDevAlias
QEMU_ARCH_I386 | \
QEMU_ARCH_LOONGARCH | \
QEMU_ARCH_MIPS | \
+ QEMU_ARCH_OPENRISC | \
QEMU_ARCH_PPC | \
QEMU_ARCH_RISCV | \
QEMU_ARCH_SH4 | \
--
2.41.0
next prev parent reply other threads:[~2024-07-05 12:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 12:45 [PATCH v2 0/2] system: Enable the device aliases for or1k, too Philippe Mathieu-Daudé
2024-07-05 12:45 ` [PATCH v2 1/2] system: Sort QEMU_ARCH_VIRTIO_PCI definition Philippe Mathieu-Daudé
2024-07-05 19:36 ` Pierrick Bouvier
2024-07-05 12:45 ` Philippe Mathieu-Daudé [this message]
2024-07-17 10:23 ` [PATCH v2 0/2] system: Enable the device aliases for or1k, too Philippe Mathieu-Daudé
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=20240705124528.97471-3-philmd@linaro.org \
--to=philmd@linaro.org \
--cc=berrange@redhat.com \
--cc=eduardo@habkost.net \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).