qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Cornelia Huck" <cohuck@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [PULL 00/17] Migration 20230209 patches
Date: Fri, 10 Feb 2023 15:21:19 +0100	[thread overview]
Message-ID: <87r0uxy528.fsf@secure.mitica> (raw)
In-Reply-To: <CAFEAcA-qSWck=ga4XBGvGXJohtGrSPO6t6+U4KqRvJdN8hrAug@mail.gmail.com> (Peter Maydell's message of "Fri, 10 Feb 2023 13:36:44 +0000")

Peter Maydell <peter.maydell@linaro.org> wrote:
> On Thu, 9 Feb 2023 at 23:35, Juan Quintela <quintela@redhat.com> wrote:
>>
>> The following changes since commit 417296c8d8588f782018d01a317f88957e9786d6:
>>
>>   tests/qtest/netdev-socket: Raise connection timeout to 60 seconds (2023-02-09 11:23:53 +0000)
>>
>> are available in the Git repository at:
>>
>>   https://gitlab.com/juan.quintela/qemu.git tags/migration-20230209-pull-request
>>
>> for you to fetch changes up to 858191aebda251a4d1e3bc77b238096673241cdd:
>>
>>   migration: Postpone postcopy preempt channel to be after main (2023-02-09 21:26:02 +0100)
>>
>> ----------------------------------------------------------------
>> Migration Pull request
>>
>> Hi
>>
>> This are all the reviewed patches for migration:
>> - AVX512 support for xbzrle (Ling Xu)
>> - /dev/userfaultd support (Peter Xu)
>> - Improve ordering of channels (Peter Xu)
>> - multifd cleanups (Li Zhang)
>> - Remove spurious files from last merge (me)
>>   Rebase makes that to you
>> - Fix mixup between state_pending_{exact,estimate} (me)
>> - Cache RAM size during migration (me)
>> - cleanup several functions (me)
>>
>> Please apply.
>>
>> ----------------------------------------------------------------
>
> Fails to build the user-mode emulators:

This is weird.

$ ls *user -d
aarch64_be-linux-user   m68k-linux-user          ppc-linux-user
aarch64-linux-user      microblazeel-linux-user  riscv32-linux-user
alpha-linux-user        microblaze-linux-user    riscv64-linux-user
armeb-linux-user        mips64el-linux-user      s390x-linux-user
arm-linux-user          mips64-linux-user        sh4eb-linux-user
bsd-user                mipsel-linux-user        sh4-linux-user
common-user             mips-linux-user          sparc32plus-linux-user
cris-linux-user         mipsn32el-linux-user     sparc64-linux-user
hexagon-linux-user      mipsn32-linux-user       sparc-linux-user
hppa-linux-user         nios2-linux-user         x86_64-linux-user
i386-linux-user         or1k-linux-user          xtensaeb-linux-user
linux-user              ppc64le-linux-user       xtensa-linux-user
loongarch64-linux-user  ppc64-linux-user


I think I build all user emulators locally.

> https://gitlab.com/qemu-project/qemu/-/jobs/3749435025
>
> In file included from ../authz/base.c:24:
> ../authz/trace.h:1:10: fatal error: trace/trace-authz.h: No such file
> or directory
> 1 | #include "trace/trace-authz.h"

This series only have one change for traces:

diff --git a/util/trace-events b/util/trace-events
index c8f53d7d9f..16f78d8fe5 100644
--- a/util/trace-events
+++ b/util/trace-events
@@ -93,6 +93,7 @@ qemu_vfio_region_info(const char *desc, uint64_t region_ofs, uint64_t region_siz
 qemu_vfio_pci_map_bar(int index, uint64_t region_ofs, uint64_t region_size, int ofs, void *host) "map region bar#%d addr 0x%"PRIx64" size 0x%"PRIx64" ofs 0x%x host %p"
 
 #userfaultfd.c
+uffd_detect_open_mode(int mode) "%d"
 uffd_query_features_nosys(int err) "errno: %i"
 uffd_query_features_api_failed(int err) "errno: %i"
 uffd_create_fd_nosys(int err) "errno: %i"

Rest of trace mentions are for the removal of migration.multifd.c.orig

And I don't play with authentication at all.

This is Fedora 37.

> https://gitlab.com/qemu-project/qemu/-/jobs/3749435094
> In file included from ../authz/simple.c:23:
> ../authz/trace.h:1:10: fatal error: trace/trace-authz.h: No such file
> or directory

Problem is that this trace file is not generated, but I can think how
any change that I did can influence this.

> 1 | #include "trace/trace-authz.h"
>
>
> https://gitlab.com/qemu-project/qemu/-/jobs/3749434963
> In file included from ../authz/listfile.c:23:
> ../authz/trace.h:1:10: fatal error: trace/trace-authz.h: No such file
> or directory
> 1 | #include "trace/trace-authz.h"

Looking at the ouptut of these, they are not informatives at all.

I am going to try to compile linux-user without system, and see if that
brings a clue.

But I don't know what is going on here.

Later, Juan.



  reply	other threads:[~2023-02-10 14:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09 23:34 [PULL 00/17] Migration 20230209 patches Juan Quintela
2023-02-09 23:34 ` [PULL 01/17] migration: Remove spurious files Juan Quintela
2023-02-09 23:34 ` [PULL 02/17] multifd: cleanup the function multifd_channel_connect Juan Quintela
2023-02-09 23:34 ` [PULL 03/17] multifd: Remove some redundant code Juan Quintela
2023-02-09 23:34 ` [PULL 04/17] linux-headers: Update to v6.1 Juan Quintela
2023-02-09 23:34 ` [PULL 05/17] util/userfaultfd: Support /dev/userfaultfd Juan Quintela
2023-02-09 23:34 ` [PULL 06/17] migration: Simplify ram_find_and_save_block() Juan Quintela
2023-02-09 23:34 ` [PULL 07/17] migration: Make find_dirty_block() return a single parameter Juan Quintela
2023-02-09 23:34 ` [PULL 08/17] migration: Split ram_bytes_total_common() in two functions Juan Quintela
2023-02-09 23:34 ` [PULL 09/17] migration: Calculate ram size once Juan Quintela
2023-02-09 23:34 ` [PULL 10/17] migration: Make ram_save_target_page() a pointer Juan Quintela
2023-02-09 23:34 ` [PULL 11/17] migration: I messed state_pending_exact/estimate Juan Quintela
2023-02-09 23:34 ` [PULL 12/17] AVX512 support for xbzrle_encode_buffer Juan Quintela
2023-02-10  7:43   ` Thomas Huth
2023-02-09 23:34 ` [PULL 13/17] Update bench-code for addressing CI problem Juan Quintela
2023-02-09 23:34 ` [PULL 14/17] migration: Rework multi-channel checks on URI Juan Quintela
2023-02-09 23:34 ` [PULL 15/17] migration: Cleanup postcopy_preempt_setup() Juan Quintela
2023-02-09 23:34 ` [PULL 16/17] migration: Add a semaphore to count PONGs Juan Quintela
2023-02-09 23:34 ` [PULL 17/17] migration: Postpone postcopy preempt channel to be after main Juan Quintela
2023-02-10 13:36 ` [PULL 00/17] Migration 20230209 patches Peter Maydell
2023-02-10 14:21   ` Juan Quintela [this message]
2023-02-10 14:33     ` Peter Maydell
2023-02-10 16:13       ` Juan Quintela
2023-02-10 16:17         ` 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=87r0uxy528.fsf@secure.mitica \
    --to=quintela@redhat.com \
    --cc=berrange@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=marcandre.lureau@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@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).