From: Vikram Garhwal <vikram.garhwal@amd.com>
To: <qemu-devel@nongnu.org>
Cc: xen-devel@lists.xenproject.org, vikram.garhwal@amd.com,
stefano.stabellini@amd.com, alex.bennee@linaro.org,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [QEMU][PATCH v4 08/10] meson.build: do not set have_xen_pci_passthrough for aarch64 targets
Date: Wed, 25 Jan 2023 00:54:05 -0800 [thread overview]
Message-ID: <20230125085407.7144-9-vikram.garhwal@amd.com> (raw)
In-Reply-To: <20230125085407.7144-1-vikram.garhwal@amd.com>
From: Stefano Stabellini <stefano.stabellini@amd.com>
have_xen_pci_passthrough is only used for Xen x86 VMs.
Signed-off-by: Stefano Stabellini <stefano.stabellini@amd.com>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
---
meson.build | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meson.build b/meson.build
index 6d3b665629..693802adb2 100644
--- a/meson.build
+++ b/meson.build
@@ -1471,6 +1471,8 @@ have_xen_pci_passthrough = get_option('xen_pci_passthrough') \
error_message: 'Xen PCI passthrough requested but Xen not enabled') \
.require(targetos == 'linux',
error_message: 'Xen PCI passthrough not available on this platform') \
+ .require(cpu == 'x86' or cpu == 'x86_64',
+ error_message: 'Xen PCI passthrough not available on this platform') \
.allowed()
--
2.17.0
next prev parent reply other threads:[~2023-01-25 8:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 8:53 [QEMU][PATCH v4 00/10] Introduce xenpvh machine for arm architecture Vikram Garhwal
2023-01-25 8:53 ` [QEMU][PATCH v4 01/10] hw/i386/xen/: move xen-mapcache.c to hw/xen/ Vikram Garhwal
2023-01-25 22:59 ` Philippe Mathieu-Daudé
2023-01-26 2:39 ` Vikram Garhwal
2023-01-25 8:53 ` [QEMU][PATCH v4 02/10] hw/i386/xen: rearrange xen_hvm_init_pc Vikram Garhwal
2023-01-25 8:54 ` [QEMU][PATCH v4 03/10] hw/i386/xen/xen-hvm: move x86-specific fields out of XenIOState Vikram Garhwal
2023-01-25 8:54 ` [QEMU][PATCH v4 04/10] xen-hvm: reorganize xen-hvm and move common function to xen-hvm-common Vikram Garhwal
2023-01-25 21:55 ` Stefano Stabellini
2023-01-25 22:38 ` Vikram Garhwal
2023-01-25 8:54 ` [QEMU][PATCH v4 05/10] include/hw/xen/xen_common: return error from xen_create_ioreq_server Vikram Garhwal
2023-01-25 21:58 ` Stefano Stabellini
2023-01-25 8:54 ` [QEMU][PATCH v4 06/10] hw/xen/xen-hvm-common: skip ioreq creation on ioreq registration failure Vikram Garhwal
2023-01-25 22:01 ` Stefano Stabellini
2023-01-25 8:54 ` [QEMU][PATCH v4 07/10] hw/xen/xen-hvm-common: Use g_new and error_setg_errno Vikram Garhwal
2023-01-25 22:07 ` Stefano Stabellini
2023-01-26 5:32 ` Frediano Ziglio
2023-01-25 8:54 ` Vikram Garhwal [this message]
2023-01-25 8:54 ` [QEMU][PATCH v4 09/10] hw/arm: introduce xenpvh machine Vikram Garhwal
2023-01-25 22:20 ` Stefano Stabellini
2023-01-26 2:44 ` Vikram Garhwal
2023-01-26 15:39 ` Stefano Stabellini
2023-01-25 8:54 ` [QEMU][PATCH v4 10/10] meson.build: enable xenpv machine build for ARM Vikram Garhwal
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=20230125085407.7144-9-vikram.garhwal@amd.com \
--to=vikram.garhwal@amd.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@amd.com \
--cc=thuth@redhat.com \
--cc=xen-devel@lists.xenproject.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).