From: Vikram Garhwal <vikram.garhwal@amd.com>
To: "Fabiano Rosas" <farosas@suse.de>,
"Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, xen-devel@lists.xenproject.org,
stefano.stabellini@amd.com,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>
Subject: Re: [QEMU][PATCH] gitlab-ci.d/crossbuilds: Drop the '--disable-tcg' configuration for xen
Date: Wed, 12 Apr 2023 08:12:03 -0700 [thread overview]
Message-ID: <41e4a106-c06b-ea29-4be4-ac46b561e17a@amd.com> (raw)
In-Reply-To: <87ile1clg8.fsf@suse.de>
Hi all,
Yes, gdbstub build issue is only for for aarch64-softmmu target and that
was the reason for this patch. x86 targets build fine with
''disable-tcg" option.
Thanks Fabiano & Philippe for sharing the existing patch series for this.
Regards,
Vikram
On 4/12/23 5:51 AM, Fabiano Rosas wrote:
> Alex Bennée <alex.bennee@linaro.org> writes:
>
>> Vikram Garhwal <vikram.garhwal@amd.com> writes:
>>
>>> Xen is supported for aarch64 via xenpvh machine. disable-tcg option fails the
>>> build for aarch64 target.
>>>
>>> Link for xen on arm patch series: https://mail.gnu.org/archive/html/qemu-devel/2023-02/msg03979.html
>>>
>>> Signed-off-by: Vikram Garhwal <vikram.garhwal@amd.com>
>>> ---
>>> .gitlab-ci.d/crossbuilds.yml | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/.gitlab-ci.d/crossbuilds.yml b/.gitlab-ci.d/crossbuilds.yml
>>> index 61b8ac86ee..6867839248 100644
>>> --- a/.gitlab-ci.d/crossbuilds.yml
>>> +++ b/.gitlab-ci.d/crossbuilds.yml
>>> @@ -186,7 +186,7 @@ cross-amd64-xen-only:
>>> variables:
>>> IMAGE: debian-amd64-cross
>>> ACCEL: xen
>>> - EXTRA_CONFIGURE_OPTS: --disable-tcg --disable-kvm
>>> + EXTRA_CONFIGURE_OPTS: --disable-kvm
>> x86 should handle --disable-tcg fine.
>>
>>>
>>> cross-arm64-xen-only:
>>> extends: .cross_accel_build_job
>>> @@ -195,4 +195,4 @@ cross-arm64-xen-only:
>>> variables:
>>> IMAGE: debian-arm64-cross
>>> ACCEL: xen
>>> - EXTRA_CONFIGURE_OPTS: --disable-tcg --disable-kvm
>>> + EXTRA_CONFIGURE_OPTS: --disable-kvm
>> Currently this builds qemu-system-i386, but with your changes and the
>> work Fabiano is doing:
>>
>> Message-Id: <20230313151058.19645-1-farosas@suse.de>
>> Date: Mon, 13 Mar 2023 12:10:48 -0300
>> Subject: [PATCH v9 00/10] target/arm: Allow CONFIG_TCG=n builds
>> From: Fabiano Rosas <farosas@suse.de>
>>
>> We should be able to have a qemu-system-aarch64 supporting Xen without TCG
> The build should already be working on current master after Philippe
> fixed the gdbstub issues. My remaining patches fix tests and general
> runtime issues. I just sent v10 to the list.
prev parent reply other threads:[~2023-04-12 15:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 21:04 [QEMU][PATCH] gitlab-ci.d/crossbuilds: Drop the '--disable-tcg' configuration for xen Vikram Garhwal
2023-04-12 5:39 ` Thomas Huth
2023-04-12 10:06 ` Philippe Mathieu-Daudé
2023-04-12 10:08 ` Alex Bennée
2023-04-12 12:51 ` Fabiano Rosas
2023-04-12 15:12 ` Vikram Garhwal [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=41e4a106-c06b-ea29-4be4-ac46b561e17a@amd.com \
--to=vikram.garhwal@amd.com \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=farosas@suse.de \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@amd.com \
--cc=thuth@redhat.com \
--cc=wainersm@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).