From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Daniel P . Berrangé" <berrange@redhat.com>,
"Fabiano Rosas" <farosas@suse.de>,
"Sebastian Ott" <sebott@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Eric Auger" <eric.auger@redhat.com>
Subject: Re: [PATCH v2 0/3] ci: Fixes on the recent cross-binary test case
Date: Thu, 8 Feb 2024 10:46:50 +0800 [thread overview]
Message-ID: <ZcRAmg4B0XD_g-IS@x1n> (raw)
In-Reply-To: <20240207005403.242235-1-peterx@redhat.com>
On Wed, Feb 07, 2024 at 08:54:00AM +0800, peterx@redhat.com wrote:
> From: Peter Xu <peterx@redhat.com>
>
> v2:
> - Fix a typo in patch 2 on QEMU_PREV_VERSION
> - Added R-bs for Dan
>
> Hi,
>
> This small patchset updates the recent cross-binary test for migration on
> a few things.
>
> Patch 1 modifies the aarch64 test GIC version to 3 rather than "max",
> paving way for enabling it, even if the CPU model is not yet ready.
>
> Patch 2 removes the tag dependency of the new build-previous-qemu job, so
> that in personal CI pipelines the job won't fail if the tag is missing, as
> reported by Peter Maydell, and solution suggested by Dan.
>
> Patch 3 updates the comment for aarch64 on the test to state the fact, and
> what is missing. Then we don't target it support for v9.0, but only until
> we have a stable CPU model for aarch64 (if ever possible to support both
> tcg and kvm).
>
> Comments welcomed, thanks.
queued.
--
Peter Xu
prev parent reply other threads:[~2024-02-08 2:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 0:54 [PATCH v2 0/3] ci: Fixes on the recent cross-binary test case peterx
2024-02-07 0:54 ` [PATCH v2 1/3] tests/migration-test: Stick with gicv3 in aarch64 test peterx
2024-02-19 11:53 ` Thomas Huth
2024-02-19 12:50 ` Peter Maydell
2024-02-19 14:13 ` Fabiano Rosas
2024-02-19 14:20 ` Thomas Huth
2024-02-07 0:54 ` [PATCH v2 2/3] ci: Remove tag dependency for build-previous-qemu peterx
2024-02-07 0:54 ` [PATCH v2 3/3] ci: Update comment for migration-compat-aarch64 peterx
2024-02-08 2:46 ` Peter Xu [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=ZcRAmg4B0XD_g-IS@x1n \
--to=peterx@redhat.com \
--cc=berrange@redhat.com \
--cc=eric.auger@redhat.com \
--cc=farosas@suse.de \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sebott@redhat.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).