qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefano Stabellini <sstabellini@kernel.org>
To: peter.maydell@linaro.org
Cc: sstabellini@kernel.org, qemu-devel@nongnu.org,
	vikram.garhwal@amd.com,
	"Stefano Stabellini" <stefano.stabellini@amd.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: [PULL v3 08/10] meson.build: do not set have_xen_pci_passthrough for aarch64 targets
Date: Tue,  2 May 2023 17:13:01 -0700	[thread overview]
Message-ID: <20230503001303.1837420-8-sstabellini@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2305021708010.974517@ubuntu-linux-20-04-desktop>

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 77d42898c8..000ef06bfa 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.25.1



  parent reply	other threads:[~2023-05-03  0:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03  0:12 [PULL v3 0/10] xenpvh3-tag Stefano Stabellini
2023-05-03  0:12 ` [PULL v3 01/10] hw/i386/xen/: move xen-mapcache.c to hw/xen/ Stefano Stabellini
2023-05-03  0:12 ` [PULL v3 02/10] hw/i386/xen: rearrange xen_hvm_init_pc Stefano Stabellini
2023-05-03  0:12 ` [PULL v3 03/10] hw/i386/xen/xen-hvm: move x86-specific fields out of XenIOState Stefano Stabellini
2023-05-03  0:12 ` [PULL v3 04/10] xen-hvm: reorganize xen-hvm and move common function to xen-hvm-common Stefano Stabellini
2023-05-03  0:12 ` [PULL v3 05/10] include/hw/xen/xen_common: return error from xen_create_ioreq_server Stefano Stabellini
2023-05-03  0:12 ` [PULL v3 06/10] hw/xen/xen-hvm-common: skip ioreq creation on ioreq registration failure Stefano Stabellini
2023-05-03  0:13 ` [PULL v3 07/10] hw/xen/xen-hvm-common: Use g_new and error_report Stefano Stabellini
2023-05-03  0:13 ` Stefano Stabellini [this message]
2023-05-03  0:13 ` [PULL v3 09/10] hw/arm: introduce xenpvh machine Stefano Stabellini
2023-05-03  0:13 ` [PULL v3 10/10] meson.build: enable xenpv machine build for ARM Stefano Stabellini
2023-05-03  7:47 ` [PULL v3 0/10] xenpvh3-tag Richard Henderson
2023-05-04  5:18   ` Vikram Garhwal
2023-05-04  6:34     ` Richard Henderson
2023-06-06 18:51       ` Garhwal, Vikram
2023-06-06 22:50         ` Richard Henderson
2023-06-06 23:12           ` 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=20230503001303.1837420-8-sstabellini@kernel.org \
    --to=sstabellini@kernel.org \
    --cc=alex.bennee@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@amd.com \
    --cc=vikram.garhwal@amd.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).