From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Prasad Pandit" <ppandit@redhat.com>
Cc: <qemu-s390x@nongnu.org>, "Halil Pasic" <pasic@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
"David Hildenbrand" <david@redhat.com>,
"Thomas Huth" <thuth@redhat.com>, "Peter Xu" <peterx@redhat.com>,
"Fabiano Rosas" <farosas@suse.de>,
"Laurent Vivier" <lvivier@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>, <qemu-devel@nongnu.org>
Subject: Re: [RFC PATCH 2/3] tests/qtest/migration-test: enable on s390x
Date: Mon, 27 May 2024 17:04:25 +1000 [thread overview]
Message-ID: <D1K8HPYOSEZN.9TWVXUFHPPO3@gmail.com> (raw)
In-Reply-To: <CAE8KmOwYPf_1rX_An0K5gncDAC7V5jvR735tEAomVJiVxOeyTg@mail.gmail.com>
On Mon May 27, 2024 at 3:46 PM AEST, Prasad Pandit wrote:
> Hi,
>
> On Sat, 25 May 2024 at 18:44, Nicholas Piggin <npiggin@gmail.com> wrote:
> > s390x is more stable now. Enable it.
> >
> > Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
> > ---
> > tests/qtest/migration-test.c | 12 ------------
> > 1 file changed, 12 deletions(-)
> >
> > diff --git a/tests/qtest/migration-test.c b/tests/qtest/migration-test.c
> > index 94d5057857..7987faaded 100644
> > --- a/tests/qtest/migration-test.c
> > +++ b/tests/qtest/migration-test.c
> > @@ -3428,16 +3428,6 @@ int main(int argc, char **argv)
> > migration_test_add("/migration/analyze-script", test_analyze_script);
> > #endif
> >
> > - /*
> > - * On s390x, the test seems to be touchy with TCG, perhaps due to race
> > - * conditions on dirty bits, so disable it there until the problems are
> > - * resolved.
> > - */
>
> -> https://lists.nongnu.org/archive/html/qemu-devel/2024-05/msg04774.html
>
> * Above patch (not reviewed yet) adds comment about sporadic problems
> on s390x, and this patch says s390x is stable now? It'll help to
> mention in the commit log - what changed to make it stable in 1 day.
Patch 1 of this series.
> * IIUC, this and the ppc64 patch above enable 'migration-test' for
> s390x and ppc64 platforms, when KVM is not available for them? ie.
> When running s390x & ppc64 migration-tests with TCG on non s390x or
> non-ppc64 machines, right? Maybe the commit message could say
> something to the effect of - enable s390x and ppc64 'migration-test'
> to run with TCG across platforms where KVM for s390x OR KVM for
> ppc64 is not available.
Yes they should be called "enable for TCG" indeed.
> > - if (g_str_equal(arch, "s390x") && !has_kvm) {
> > - g_test_message("Skipping tests: s390x host with KVM is required");
> > - goto test_add_done;
> > - }
> > -
> > if (is_x86) {
> > migration_test_add("/migration/precopy/unix/suspend/live",
> > test_precopy_unix_suspend_live);
> > @@ -3619,8 +3609,6 @@ int main(int argc, char **argv)
> > test_vcpu_dirty_limit);
> > }
> >
> > -test_add_done:
> > -
> > ret = g_test_run();
> >
> > g_assert_cmpint(ret, ==, 0);
> > --
>
> * Otherwise, the change looks okay to enable 'migration-test' for
> s390x with TCG IIUC.
Thanks,
Nick
next prev parent reply other threads:[~2024-05-27 7:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-25 13:12 [RFC PATCH 0/3] Fix s390x flic migration and add some more qtests Nicholas Piggin
2024-05-25 13:12 ` [RFC PATCH 1/3] hw/intc/s390_flic: Migrate pending state Nicholas Piggin
2024-05-26 15:53 ` David Hildenbrand
2024-05-26 19:44 ` Richard Henderson
2024-05-26 20:33 ` David Hildenbrand
2024-05-27 5:51 ` Thomas Huth
2024-05-27 7:11 ` Nicholas Piggin
2024-05-25 13:12 ` [RFC PATCH 2/3] tests/qtest/migration-test: enable on s390x Nicholas Piggin
2024-05-27 5:46 ` Prasad Pandit
2024-05-27 7:04 ` Nicholas Piggin [this message]
2024-05-27 7:40 ` Prasad Pandit
2024-05-25 13:12 ` [RFC PATCH 3/3] tests/qtest/migration-test: Enable test_ignore_shared Nicholas Piggin
2024-05-27 12:42 ` Fabiano Rosas
2024-05-27 14:56 ` Peter Xu
2024-05-27 15:11 ` Fabiano Rosas
2024-05-27 15:41 ` Peter Xu
2024-05-27 7:13 ` [RFC PATCH 0/3] Fix s390x flic migration and add some more qtests Thomas Huth
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=D1K8HPYOSEZN.9TWVXUFHPPO3@gmail.com \
--to=npiggin@gmail.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=farosas@suse.de \
--cc=lvivier@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@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).