All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabiano Rosas <farosas@suse.de>
To: Michael Tokarev <mjt@tls.msk.ru>, Thomas Huth <thuth@redhat.com>,
	qemu-devel@nongnu.org
Cc: Peter Xu <peterx@redhat.com>, qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PATCH v3 3/7] migration: Fix parsing of s390 stream
Date: Mon, 13 Jan 2025 10:07:34 -0300	[thread overview]
Message-ID: <87bjwahnft.fsf@suse.de> (raw)
In-Reply-To: <87ed16hnnd.fsf@suse.de>

Fabiano Rosas <farosas@suse.de> writes:

> Michael Tokarev <mjt@tls.msk.ru> writes:
>
>> 13.01.2025 11:19, Thomas Huth wrote:
>>> On 13/01/2025 08.51, Michael Tokarev wrote:
>>
>>>> Picked up:
>>>>
>>>>   1/7 migration: Add more error handling to analyze-migration.py
>>>>   3/7 migration: Fix parsing of s390 stream
>>>>   7/7 s390x: Fix CSS migration
>>>>
>>>> but still getting the same error:
>>>>
>>>>   https://gitlab.com/mjt0k/qemu/-/jobs/8832218999 (9.2 branch)
>>>>   https://gitlab.com/mjt0k/qemu/-/jobs/8832224338 (9.1 branch)
>>> 
>>> Blindly guessing: You need now patch 4/7 and 5/7, too? ... hopefully Fabiano could reply and point you to the exact set of patches that you need...
>>
>> Yes, after picking up ALL 7 out of 7 in this patchset (b/c even the
>> trivial 2/7, "migration: Remove unused argument in vmsd_desc_field_end",
>> is needed or else the subsequent fixes doesn't apply) it is now green
>> finally, eg, https://gitlab.com/mjt0k/qemu/-/jobs/8832849813
>>
>> Fabiano, what do you think, - should the whole patchset be picked up
>> for 9.2 and 9.1?
>
> Yeah, sorry, I was focused on unbreaking the migration PR and added a
> bunch of patches without thinking of stable.
>
> So the s390x regression (1/7) is 9.1, but 9.0 already had the broken

7/7

> analyze-script.py (3/7) and the broken array compression code (4-6/7).
>
> We definitely need 1/7 for 9.1 and 9.2. The rest of the series is "just"

7/7

> to avoid breaking the tests. If you can apply it easily I think that's
> preferable. Otherwise maybe we could disable the analyze-migration.py
> test for stable? I can also work on a backport if needed. Let me know
> what you prefer.
>
>>
>> Thanks,
>>
>> /mjt


  reply	other threads:[~2025-01-13 13:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09 18:52 [PATCH v3 0/7] migration: Fix s390 regressions + migration script Fabiano Rosas
2025-01-09 18:52 ` [PATCH v3 1/7] migration: Add more error handling to analyze-migration.py Fabiano Rosas
2025-01-09 18:52 ` [PATCH v3 2/7] migration: Remove unused argument in vmsd_desc_field_end Fabiano Rosas
2025-01-09 18:52 ` [PATCH v3 3/7] migration: Fix parsing of s390 stream Fabiano Rosas
2025-01-12 13:06   ` Michael Tokarev
2025-01-12 14:29     ` Michael Tokarev
2025-01-13  6:39       ` Thomas Huth
2025-01-13  7:51         ` Michael Tokarev
2025-01-13  8:19           ` Thomas Huth
2025-01-13  9:09             ` Michael Tokarev
2025-01-13 13:03               ` Fabiano Rosas
2025-01-13 13:07                 ` Fabiano Rosas [this message]
2025-01-13 15:13                 ` Michael Tokarev
2025-01-09 18:52 ` [PATCH v3 4/7] migration: Rename vmstate_info_nullptr Fabiano Rosas
2025-01-09 19:10   ` Peter Xu
2025-01-09 18:52 ` [PATCH v3 5/7] migration: Dump correct JSON format for nullptr replacement Fabiano Rosas
2025-01-09 18:52 ` [PATCH v3 6/7] migration: Fix arrays of pointers in JSON writer Fabiano Rosas
2025-01-09 19:10   ` Peter Xu
2025-01-09 18:52 ` [PATCH v3 7/7] s390x: Fix CSS migration Fabiano Rosas
2025-01-12 14:34   ` Michael Tokarev
2025-01-13  6:37     ` Thomas Huth
2025-01-12 14:34   ` Michael Tokarev

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=87bjwahnft.fsf@suse.de \
    --to=farosas@suse.de \
    --cc=mjt@tls.msk.ru \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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 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.