From: Cleber Rosa <crosa@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>, QEMU <qemu-devel@nongnu.org>
Subject: Re: [PATCH 2/2] analyze-migration.py: replace numpy with python 3.2
Date: Tue, 10 Dec 2019 12:49:09 -0500 [thread overview]
Message-ID: <20191210174909.GA4230@dhcp-17-72.bos.redhat.com> (raw)
In-Reply-To: <CAJ+F1CL_0ytd2O4m1FcqQbFSLh3S5v=fLY=FyUZa4zg47uCOQA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3356 bytes --]
On Tue, Dec 10, 2019 at 02:14:18PM +0400, Marc-André Lureau wrote:
> Hi
>
> On Tue, Dec 10, 2019 at 6:59 AM Eduardo Habkost <ehabkost@redhat.com> wrote:
> >
> > On Fri, Dec 06, 2019 at 09:27:23AM -0500, Cleber Rosa wrote:
> > > On Wed, Nov 27, 2019 at 02:10:38PM +0400, Marc-André Lureau wrote:
> > > > Use int.from_bytes() from python 3.2 instead.
> > > >
> > > > Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> > > > ---
> > > > scripts/analyze-migration.py | 35 +++++++++++++++++++----------------
> > > > 1 file changed, 19 insertions(+), 16 deletions(-)
> > > >
> > > > diff --git a/scripts/analyze-migration.py b/scripts/analyze-migration.py
> > > > index 2b835d9b70..96a31d3974 100755
> > > > --- a/scripts/analyze-migration.py
> > > > +++ b/scripts/analyze-migration.py
> > > > @@ -1,4 +1,4 @@
> > > > -#!/usr/bin/env python
> > > > +#!/usr/bin/env python3
> > [...]
> > >
> > > Marc-André, I couldn't yet pinpoint the reason yet, but this patch
> > > changes the parsing of bool fields. This is a diff between the output
> > > pre/post this patch on the same images:
> > >
> > > $ diff -u out_x8664_pre out_x8664_post
> > > --- out_x8664_pre 2019-12-06 09:14:16.128943264 -0500
> > > +++ out_x8664_post 2019-12-06 09:23:35.861378600 -0500
> > > @@ -3039,7 +3039,7 @@
> > > "mac_reg[RADV]": "0x00000000",
> > > "mac_reg[TADV]": "0x00000000",
> > > "mac_reg[ITR]": "0x00000000",
> > > - "mit_irq_level": true
> > > + "mit_irq_level": false
> > > },
> > > "e1000/full_mac_state": {
> > > "mac_reg": [
> > > @@ -36010,10 +36010,10 @@
> > > ],
> > > "smb_auxctl": "0x02",
> > > "smb_blkdata": "0x00",
> > > - "i2c_enable": true,
> > > + "i2c_enable": false,
> > > "op_done": true,
> > > - "in_i2c_block_read": true,
> > > - "start_transaction_on_status_read": true
> > > + "in_i2c_block_read": false,
> > > + "start_transaction_on_status_read": false
> > > },
> > > "ar.tmr.timer": "ff ff ff ff ff ff ff ff",
> > > "ar.tmr.overflow_time": "0x0000000000000000",
> > >
> > > This true/false flipping is consistent across various images (tried on
> > > images generated on a few other targets).
> >
> > It looks like moving to python3 accidentally fixes a bug.
> >
> > This is VMSDFieldBool.read:
> >
> > def read(self):
> > super(VMSDFieldBool, self).read()
> > if self.data[0] == 0:
> > self.data = False
> > else:
> > self.data = True
> > return self.data
> >
> > On python2, MigrationFile.readvar() returned a string, so the
> > (self.data[0] == 0) check was never true. This means all boolean
> > fields were always initialized to True.
> >
> > On python3, MigrationFile.readvar() returns a bytearray, so the
> > (self.data[0] == 0) check now works as expected.
>
> Ah! nice surprise. Do you mind updating the commit message on commit?
> Or should I resend?
>
> thanks
>
> --
> Marc-André Lureau
>
Yep, I'm queueing this with an updated commit message.
Eduardo, does your comment imply a "Reviewed-by"?
Cheers,
- Cleber.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-12-10 17:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 10:10 [PATCH 0/2] analyze-migration.py: require python 3 Marc-André Lureau
2019-11-27 10:10 ` [PATCH 1/2] analyze-migration.py: fix find() type error Marc-André Lureau
2019-11-27 23:37 ` Eduardo Habkost
2019-11-27 10:10 ` [PATCH 2/2] analyze-migration.py: replace numpy with python 3.2 Marc-André Lureau
2019-12-06 14:27 ` Cleber Rosa
2019-12-10 2:58 ` Eduardo Habkost
2019-12-10 10:14 ` Marc-André Lureau
2019-12-10 17:49 ` Cleber Rosa [this message]
2019-12-10 17:57 ` Cleber Rosa
2019-12-10 19:26 ` Eduardo Habkost
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=20191210174909.GA4230@dhcp-17-72.bos.redhat.com \
--to=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=qemu-devel@nongnu.org \
/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).