From: Richard Henderson <richard.henderson@linaro.org>
To: "Garhwal, Vikram" <vikram.garhwal@amd.com>,
Stefano Stabellini <sstabellini@kernel.org>,
"peter.maydell@linaro.org" <peter.maydell@linaro.org>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [PULL v3 0/10] xenpvh3-tag
Date: Tue, 6 Jun 2023 15:50:08 -0700 [thread overview]
Message-ID: <7465b3c6-ecf9-bf17-2504-2338bbef27b7@linaro.org> (raw)
In-Reply-To: <MN2PR12MB440877291659B9B55ADC0CF79F52A@MN2PR12MB4408.namprd12.prod.outlook.com>
On 6/6/23 11:51, Garhwal, Vikram wrote:
> Hi Richard,
>
> I fixed the tsan-build issue but now seeing another issue with “—disable-tcg” option for
> cross builds xen. Here is the build failure message:
> "include/tcg/oversized-guest.h:10:10: fatal error: tcg-target-reg-bits.h: No such file or
> directory
>
> 10 | #include "tcg-target-reg-bits.h”
>
>
>
> Full log for build fail: https://gitlab.com/Vikram.garhwal/qemu-ioreq/-/jobs/4416773231
> <https://gitlab.com/Vikram.garhwal/qemu-ioreq/-/jobs/4416773231>.
>
> This is my last patch which enables xen build for ARM:
> https://gitlab.com/Vikram.garhwal/qemu-ioreq/-/commit/6f6667217bfc14ff5504ee5fdee23a948d60fb7f <https://gitlab.com/Vikram.garhwal/qemu-ioreq/-/commit/6f6667217bfc14ff5504ee5fdee23a948d60fb7f>.
>
> This seems something missing in disable-tcg config for ARM builds. Any hints on what might
> be causing this TCG issue?
>
> Thanks in advance for your help!
I meant to cc you, but fix here:
https://patchew.org/QEMU/20230606224609.208550-1-richard.henderson@linaro.org/
r~
next prev parent reply other threads:[~2023-06-06 22:50 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 ` [PULL v3 08/10] meson.build: do not set have_xen_pci_passthrough for aarch64 targets Stefano Stabellini
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 [this message]
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=7465b3c6-ecf9-bf17-2504-2338bbef27b7@linaro.org \
--to=richard.henderson@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--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).