From: Paolo Bonzini <pbonzini@redhat.com>
To: "Sunil Muthuswamy" <sunilmut@microsoft.com>,
"Stefan Weil" <sw@weilnetz.de>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [PATCH] WHPX: Fix WHPX build break
Date: Thu, 22 Oct 2020 03:16:00 +0200 [thread overview]
Message-ID: <6530a0a3-2d98-89f5-414e-8bd4400e0be2@redhat.com> (raw)
In-Reply-To: <SN4PR2101MB0880D706A85793DDFC411304C01D0@SN4PR2101MB0880.namprd21.prod.outlook.com>
On 22/10/20 02:27, Sunil Muthuswamy wrote:
> With upstream commit#8a19980e3fc4, logic was introduced to only
> allow WHPX build on x64. But, the logic checks for the cpu family
> and not the cpu. On my fedora container build, the cpu family is
> x86 and the cpu is x86_64. Fixing the build break by checking for
> the cpu, instead of the cpu family.
>
> Signed-off-by: Sunil Muthuswamy <sunilmut@microsoft.com>
> ---
> meson.build | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meson.build b/meson.build
> index 7627a0ae46..2d84e90495 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -198,7 +198,7 @@ else
> have_xen_pci_passthrough = false
> endif
> if not get_option('whpx').disabled() and targetos == 'windows'
> - if get_option('whpx').enabled() and cpu != 'x86_64'
> + if get_option('whpx').enabled() and host_machine.cpu() != 'x86_64'
> error('WHPX requires 64-bit host')
> elif cc.has_header('WinHvPlatform.h', required: get_option('whpx')) and \
> cc.has_header('WinHvEmulation.h', required: get_option('whpx'))
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2020-10-22 1:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 0:27 [PATCH] WHPX: Fix WHPX build break Sunil Muthuswamy
2020-10-22 1:16 ` Paolo Bonzini [this message]
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=6530a0a3-2d98-89f5-414e-8bd4400e0be2@redhat.com \
--to=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sunilmut@microsoft.com \
--cc=sw@weilnetz.de \
/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).