From: Peter Xu <peterx@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Juan Quintela" <quintela@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>,
zhengchuan@huawei.com, "Stefan Hajnoczi" <stefanha@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PULL 00/10] migration queue
Date: Thu, 15 Oct 2020 14:58:35 -0400 [thread overview]
Message-ID: <20201015185835.GC133059@xz-x1> (raw)
In-Reply-To: <821ef4ae-1e66-02b9-d9ae-567005aa7c2f@redhat.com>
On Thu, Oct 15, 2020 at 11:13:44AM +0200, Thomas Huth wrote:
> On 14/10/2020 22.01, Peter Xu wrote:
> > On Sun, Oct 11, 2020 at 07:29:25PM +0100, Peter Maydell wrote:
> >>> Migration:
> >>> Dirtyrate measurement API cleanup
> >>> Postcopy recovery fixes
> >>>
> >>> Virtiofsd:
> >>> Missing qemu_init_exec_dir call
> >>> Support for setting the group on socket creation
> >>> Stop a gcc warning
> >>> Avoid tempdir in sandboxing
> >>
> >> This seems to hang in 'make check' trying to run
> >> tests/qtest/migration-test on s390x and ppc, ie
> >> the big-endian hosts.
> >
> > Hi, Peter,
> >
> > Do you know what's the page size on both platforms?
>
> s390x uses 4k page size by default. Only huge-pages are different.
Hmm... Then I can't explain. Maybe there're two bugs, or maybe there's
something I've overlooked.
>
> > I'm also trying to find a s390x host to give it a shot. However I decided to
> > also ask this loud so it might be even faster.
>
> Easiest way to test on s390x is likely to use Travis. If you have already an
> github or gitlab account, you can simply clone the qemu repository there and
> add Travis (from the Marketplace in Github, not sure how it exactly works
> with Gitlab) to your cloned repo. If you then push commits to a branch,
> Travis should trigger automatically, including runs on s390x, see e.g.:
>
> https://travis-ci.com/github/huth/qemu/jobs/399317194
Finally I setup the CI this time and that's quite handy. I should probably do
this even earlier, thanks Thomas!
Anyway, I'll see whether my fix will pass travis (still running), and see
whether I should repost again.
--
Peter Xu
next prev parent reply other threads:[~2020-10-15 19:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 19:10 [PULL 00/10] migration queue Dr. David Alan Gilbert (git)
2020-10-08 19:10 ` [PULL 01/10] virtiofsd: Silence gcc warning Dr. David Alan Gilbert (git)
2020-10-08 19:10 ` [PULL 02/10] tools/virtiofsd: add support for --socket-group Dr. David Alan Gilbert (git)
2020-10-08 19:10 ` [PULL 03/10] virtiofsd: Call qemu_init_exec_dir Dr. David Alan Gilbert (git)
2020-10-08 19:10 ` [PULL 04/10] virtiofsd: avoid /proc/self/fd tempdir Dr. David Alan Gilbert (git)
2020-10-08 19:10 ` [PULL 05/10] migration: Pass incoming state into qemu_ufd_copy_ioctl() Dr. David Alan Gilbert (git)
2020-10-08 19:10 ` [PULL 06/10] migration: Introduce migrate_send_rp_message_req_pages() Dr. David Alan Gilbert (git)
2020-10-08 19:10 ` [PULL 07/10] migration: Maintain postcopy faulted addresses Dr. David Alan Gilbert (git)
2020-10-08 19:10 ` [PULL 08/10] migration: Sync requested pages after postcopy recovery Dr. David Alan Gilbert (git)
2020-10-08 19:10 ` [PULL 09/10] migration/dirtyrate: record start_time and calc_time while at the measuring state Dr. David Alan Gilbert (git)
2020-10-08 19:10 ` [PULL 10/10] migration/dirtyrate: present dirty rate only when querying the rate has completed Dr. David Alan Gilbert (git)
2020-10-11 18:29 ` [PULL 00/10] migration queue Peter Maydell
2020-10-12 8:12 ` Dr. David Alan Gilbert
2020-10-14 20:01 ` Peter Xu
2020-10-15 9:13 ` Thomas Huth
2020-10-15 18:58 ` Peter Xu [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-07 15:55 Dr. David Alan Gilbert (git)
2020-10-08 16:18 ` Peter Maydell
2020-10-08 16:31 ` Dr. David Alan Gilbert
2020-10-08 17:09 ` Eric Blake
2020-10-08 17:43 ` Peter Xu
2020-10-08 18:51 ` Peter Xu
2020-10-08 19:09 ` Dr. David Alan Gilbert
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=20201015185835.GC133059@xz-x1 \
--to=peterx@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=dgilbert@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
--cc=zhengchuan@huawei.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).