From: Fabiano Rosas <farosas@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>,
Stefano Stabellini <sstabellini@kernel.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [PULL v2 0/10] xenpvh
Date: Wed, 15 Feb 2023 17:05:40 -0300 [thread overview]
Message-ID: <87bkluelt7.fsf@suse.de> (raw)
In-Reply-To: <CAFEAcA96Mb5KAdPQrncqh9SM2iRc7aE2f4deoiF_2vChdMF0rw@mail.gmail.com>
Peter Maydell <peter.maydell@linaro.org> writes:
> On Tue, 14 Feb 2023 at 23:43, Stefano Stabellini <sstabellini@kernel.org> wrote:
>>
>> The following changes since commit 6a50f64ca01d0a7b97f14f069762bfd88160f31e:
>>
>> Merge tag 'pull-request-2023-02-14' of https://gitlab.com/thuth/qemu into staging (2023-02-14 14:46:10 +0000)
>>
>> are available in the Git repository at:
>>
>> https://gitlab.com/sstabellini/qemu xenpvh2
>>
>> for you to fetch changes up to 86b01d58ca2840bea6e4e7260aad450a660fbd46:
>>
>> meson.build: enable xenpv machine build for ARM (2023-02-14 15:39:25 -0800)
>>
>> ----------------------------------------------------------------
>
> Fails to compile for some configs, eg:
>
> https://gitlab.com/qemu-project/qemu/-/jobs/3775820949
> https://gitlab.com/qemu-project/qemu/-/jobs/3775820984
>
> In file included from ../target/arm/machine.c:6:
> ../target/arm/internals.h:1141:21: error: field ‘f’ has incomplete type
> 1141 | CPUTLBEntryFull f;
>
For this to work we'll probably need to cherry-pick some parts of my
disable-tcg series:
https://lore.kernel.org/r/20230213202927.28992-1-farosas@suse.de
For this error specifically, patch 16.
And when the build eventually succeeds we might have make check
issues. We just encountered an analogous problem on an aarch64 host: Xen
brings qemu-system-x86_64 on an aarch64 host and tests fail because
there's no TCG.
next prev parent reply other threads:[~2023-02-15 20:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 23:43 [PULL v2 0/10] xenpvh Stefano Stabellini
2023-02-14 23:43 ` [PULL v2 01/10] hw/i386/xen/: move xen-mapcache.c to hw/xen/ Stefano Stabellini
2023-02-14 23:43 ` [PULL v2 02/10] hw/i386/xen: rearrange xen_hvm_init_pc Stefano Stabellini
2023-02-14 23:43 ` [PULL v2 03/10] hw/i386/xen/xen-hvm: move x86-specific fields out of XenIOState Stefano Stabellini
2023-02-14 23:43 ` [PULL v2 04/10] xen-hvm: reorganize xen-hvm and move common function to xen-hvm-common Stefano Stabellini
2023-02-14 23:43 ` [PULL v2 05/10] include/hw/xen/xen_common: return error from xen_create_ioreq_server Stefano Stabellini
2023-02-14 23:43 ` [PULL v2 06/10] hw/xen/xen-hvm-common: skip ioreq creation on ioreq registration failure Stefano Stabellini
2023-02-14 23:43 ` [PULL v2 07/10] hw/xen/xen-hvm-common: Use g_new and error_report Stefano Stabellini
2023-02-14 23:43 ` [PULL v2 08/10] meson.build: do not set have_xen_pci_passthrough for aarch64 targets Stefano Stabellini
2023-02-14 23:43 ` [PULL v2 09/10] hw/arm: introduce xenpvh machine Stefano Stabellini
2023-02-14 23:43 ` [PULL v2 10/10] meson.build: enable xenpv machine build for ARM Stefano Stabellini
2023-02-15 18:36 ` [PULL v2 0/10] xenpvh Peter Maydell
2023-02-15 20:05 ` Fabiano Rosas [this message]
2023-02-15 21:17 ` Stefano Stabellini
2023-02-16 17:15 ` Peter Maydell
2023-02-16 12:59 ` Fabiano Rosas
2023-02-16 17:17 ` Peter Maydell
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=87bkluelt7.fsf@suse.de \
--to=farosas@suse.de \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.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).