From: "Alex Bennée" <alex.bennee@linaro.org>
To: quintela@redhat.com
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Alexey Perevalov" <a.perevalov@samsung.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Peter Xu" <peterx@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PULL 00/27] Migration pull
Date: Mon, 22 Jan 2018 18:38:41 +0000 [thread overview]
Message-ID: <87h8rdkaby.fsf@linaro.org> (raw)
In-Reply-To: <87h8rg2jdh.fsf@secure.laptop>
Juan Quintela <quintela@redhat.com> writes:
> Peter Maydell <peter.maydell@linaro.org> wrote:
>> On 19 January 2018 at 16:43, Alexey Perevalov <a.perevalov@samsung.com> wrote:
>>> As I remember, I tested build in QEMU's docker build system,
>>> but now I checked it on i386 Ubuntu, and yes linker says about unresolved
>>> atomic symbols. Next week, I'll have a time to investigate it deeper.
>>
>> This sounds like exactly the problem I pointed out in a previous
>> round of this patchset :-(
>>
>> https://lists.gnu.org/archive/html/qemu-devel/2018-01/msg02103.html
>>
>> Ignoring comments and sending patches anyway makes me grumpy,
>> especially when the result is exactly "fails obscurely on
>> some architectures only"...
>
> It compiles for me. F25 i686 gcc. I did change it to use intptr_t
> instead of uint64_t. So, I don't know what is going on here.
>
> Then, I have a report that clang -m32 didn't work (Mat). I haven't been
> able yet to reproduce. I don't have 32bits libraries installed on my
> x86_64 systems. clang compiles for me on both 64 bits (f27) and 32bits
> native (f25, it is a long history that it is not f27).
>
> So, I can agree that we have to fix anything that don't work, but I
> can't agree that I didn't care about comments, at least I tried to fix
> the problems you pointed me to.
>
> What I don't have is an easier way of compiling on arm and ppc32, but I
> will search a way to do that for my pull requsets.
make docker-test-build@debian-armhf-cross
make docker-test-build@debian-powerpc-cross
Assuming you have docker setup and working.
>
> Sorry about the inconveniences.
>
> Later, Juan.
--
Alex Bennée
next prev parent reply other threads:[~2018-01-22 18:38 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 11:52 [Qemu-devel] [PULL 00/27] Migration pull Juan Quintela
2018-01-15 11:52 ` [Qemu-devel] [PULL 01/27] migration: Use proper types in json Juan Quintela
2018-01-15 11:52 ` [Qemu-devel] [PULL 02/27] migration: print features as on off Juan Quintela
2018-01-15 11:52 ` [Qemu-devel] [PULL 03/27] migration: free addr in the same function that we created it Juan Quintela
2018-01-15 11:52 ` [Qemu-devel] [PULL 04/27] docs: Convert migration.txt to rst Juan Quintela
2018-01-15 11:52 ` [Qemu-devel] [PULL 05/27] migration: free result string Juan Quintela
2018-01-15 11:52 ` [Qemu-devel] [PULL 06/27] migration: fix analyze-migration.py script with radix table Juan Quintela
2018-01-15 11:52 ` [Qemu-devel] [PULL 07/27] migration: introduce postcopy-blocktime capability Juan Quintela
2018-01-15 11:52 ` [Qemu-devel] [PULL 08/27] migration: add postcopy blocktime ctx into MigrationIncomingState Juan Quintela
2018-01-15 11:52 ` [Qemu-devel] [PULL 09/27] migration: calculate vCPU blocktime on dst side Juan Quintela
2018-01-15 20:19 ` Max Reitz
2018-01-16 13:19 ` Juan Quintela
2018-01-16 17:43 ` Dr. David Alan Gilbert
2018-01-16 19:22 ` Alexey Perevalov
2018-01-15 11:52 ` [Qemu-devel] [PULL 10/27] migration: postcopy_blocktime documentation Juan Quintela
2018-01-15 11:52 ` [Qemu-devel] [PULL 11/27] migration: add blocktime calculation into migration-test Juan Quintela
2018-01-15 11:52 ` [Qemu-devel] [PULL 12/27] migration: add postcopy total blocktime into query-migrate Juan Quintela
2018-01-15 11:52 ` [Qemu-devel] [PULL 13/27] migration: Guard ram_bytes_remaining against early call Juan Quintela
2018-01-15 11:52 ` [Qemu-devel] [PULL 14/27] migration: finalize current_migration object Juan Quintela
2018-01-15 11:52 ` [Qemu-devel] [PULL 15/27] migration: assert colo instead of check Juan Quintela
2018-01-15 11:52 ` [Qemu-devel] [PULL 16/27] migration: qemu_savevm_state_cleanup() in cleanup Juan Quintela
2018-01-15 11:52 ` [Qemu-devel] [PULL 17/27] migration: remove "enable_colo" var Juan Quintela
2018-01-15 11:53 ` [Qemu-devel] [PULL 18/27] migration: split use of MigrationState.total_time Juan Quintela
2018-01-15 11:53 ` [Qemu-devel] [PULL 19/27] migration: move vm_old_running into global state Juan Quintela
2018-01-15 11:53 ` [Qemu-devel] [PULL 20/27] migration: introduce downtime_start Juan Quintela
2018-01-15 11:53 ` [Qemu-devel] [PULL 21/27] migration: introduce migrate_calculate_complete Juan Quintela
2018-01-15 11:53 ` [Qemu-devel] [PULL 22/27] migration: use switch at the end of migration Juan Quintela
2018-01-15 11:53 ` [Qemu-devel] [PULL 23/27] migration: cleanup stats update into function Juan Quintela
2018-01-15 11:53 ` [Qemu-devel] [PULL 24/27] migration: major cleanup for migrate iterations Juan Quintela
2018-01-15 11:53 ` [Qemu-devel] [PULL 25/27] migration: put the finish part into a new function Juan Quintela
2018-01-15 11:53 ` [Qemu-devel] [PULL 26/27] migration: remove some block_cleanup_parameters() Juan Quintela
2018-01-15 11:53 ` [Qemu-devel] [PULL 27/27] migration: remove notify in fd_error Juan Quintela
2018-01-15 16:14 ` [Qemu-devel] [PULL 00/27] Migration pull Peter Maydell
2018-01-19 16:27 ` Philippe Mathieu-Daudé
2018-01-19 16:34 ` Peter Maydell
2018-01-19 17:00 ` Philippe Mathieu-Daudé
2018-01-19 16:43 ` Alexey Perevalov
2018-01-19 17:01 ` Peter Maydell
2018-01-20 23:36 ` Juan Quintela
2018-01-21 3:19 ` Philippe Mathieu-Daudé
2018-01-22 10:03 ` Peter Maydell
2018-01-22 16:25 ` Alexey Perevalov
2018-01-22 16:26 ` Peter Maydell
2018-01-22 18:25 ` Alexey Perevalov
2018-01-22 19:52 ` Dr. David Alan Gilbert
2018-01-22 18:38 ` Alex Bennée [this message]
2018-01-22 12:22 ` Peter Maydell
2018-01-22 12:38 ` Dr. David Alan Gilbert
2018-01-22 13:38 ` Peter Maydell
2018-01-23 10:09 ` 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=87h8rdkaby.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=a.perevalov@samsung.com \
--cc=dgilbert@redhat.com \
--cc=f4bug@amsat.org \
--cc=lvivier@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.