From: Peter Xu <peterx@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>,
John Snow <jsnow@redhat.com>, Cleber Rosa <crosa@redhat.com>
Subject: Re: [PATCH] analyze-migration: ignore RAM_SAVE_FLAG_MULTIFD_FLUSH
Date: Tue, 3 Oct 2023 17:08:55 -0400 [thread overview]
Message-ID: <ZRyC5+juhdOrP73K@x1n> (raw)
In-Reply-To: <CAJ+F1C+r3Nz9vCUhkzRAdsGPZexW8ivcO2E=CFK1jhkUvOfPxA@mail.gmail.com>
On Wed, Sep 27, 2023 at 02:32:37PM +0400, Marc-André Lureau wrote:
> On Tue, Sep 26, 2023 at 12:19 PM <marcandre.lureau@redhat.com> wrote:
> >
> > From: Marc-André Lureau <marcandre.lureau@redhat.com>
> >
> > Traceback (most recent call last):
> > File "scripts/analyze-migration.py", line 605, in <module>
> > dump.read(dump_memory = args.memory)
> > File "scripts/analyze-migration.py", line 542, in read
> > section.read()
> > File "scripts/analyze-migration.py", line 214, in read
> > raise Exception("Unknown RAM flags: %x" % flags)
> > Exception: Unknown RAM flags: 200
> >
> > See commit 77c259a4cb ("multifd: Create property multifd-flush-after-each-section")
> >
> > Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
>
> cc Peter and Juan
Sorry to be late..
It's actually a bug to have MULTIFD_FLUSH in the stream in the first place,
though.. the fix to make that MULTIFD_FLUSH disappear should be in Juan's
next pull.
IIUC logically analyze-migration.py shouldn't be able to understand
multifd, because it relies on a solo stream file, while multifd is already
against it. We plan to add "file:" support for multifd, but even with that
I doubt whether there'll be MULTIFD_FLUSH kept in the final file because
it's only used to sync threads.
Thanks,
>
> > ---
> > scripts/analyze-migration.py | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/scripts/analyze-migration.py b/scripts/analyze-migration.py
> > index b82a1b0c58..082424558b 100755
> > --- a/scripts/analyze-migration.py
> > +++ b/scripts/analyze-migration.py
> > @@ -111,6 +111,8 @@ class RamSection(object):
> > RAM_SAVE_FLAG_CONTINUE = 0x20
> > RAM_SAVE_FLAG_XBZRLE = 0x40
> > RAM_SAVE_FLAG_HOOK = 0x80
> > + RAM_SAVE_FLAG_COMPRESS_PAGE = 0x100
> > + RAM_SAVE_FLAG_MULTIFD_FLUSH = 0x200
> >
> > def __init__(self, file, version_id, ramargs, section_key):
> > if version_id != 4:
> > @@ -205,6 +207,8 @@ def read(self):
> > raise Exception("XBZRLE RAM compression is not supported yet")
> > elif flags & self.RAM_SAVE_FLAG_HOOK:
> > raise Exception("RAM hooks don't make sense with files")
> > + if flags & self.RAM_SAVE_FLAG_MULTIFD_FLUSH:
> > + continue
> >
> > # End of RAM section
> > if flags & self.RAM_SAVE_FLAG_EOS:
> > --
> > 2.41.0
> >
> >
>
>
> --
> Marc-André Lureau
>
--
Peter Xu
next prev parent reply other threads:[~2023-10-03 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 8:18 [PATCH] analyze-migration: ignore RAM_SAVE_FLAG_MULTIFD_FLUSH marcandre.lureau
2023-09-27 10:32 ` Marc-André Lureau
2023-10-03 21:08 ` Peter Xu [this message]
2023-09-27 19:58 ` Fabiano Rosas
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=ZRyC5+juhdOrP73K@x1n \
--to=peterx@redhat.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=marcandre.lureau@gmail.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 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).