All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
	qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	pkrempa@redhat.com, Eduardo Habkost <ehabkost@redhat.com>,
	qemu-block@nongnu.org, Markus Armbruster <armbru@redhat.com>,
	Max Reitz <mreitz@redhat.com>, Cleber Rosa <crosa@redhat.com>
Subject: Re: [PATCH 3/6] iotests: move bitmap helpers into their own file
Date: Tue, 3 Mar 2020 16:55:19 -0500	[thread overview]
Message-ID: <65874958-de03-a7f3-ea20-914f38468a5d@redhat.com> (raw)
In-Reply-To: <9870b153-f2a9-44dd-9967-228d158dabcb@virtuozzo.com>



On 2/27/20 5:54 AM, Vladimir Sementsov-Ogievskiy wrote:
> 
> Clean code movement, no changes. If test passes, it should be correct :)
> 
> The only thing: I'd prefer not exporting global variables and use
> bitmaps.GROUPS instead (even then, it's not very good interface but..)
> 
> with or without it:
> Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>

Hm, yeah -- it's not great, it's definitely just a bit of a quick
shuffle instead of a more serious effort at a refactor to provide bitmap
services for all tests.

I don't think it's worth the time just yet to make a serious attempt at
making this module bigger -- but maybe there is work that can be done at
providing bitmap management services targeted for use outside of testing
code. (i.e. into the python/ folder somewhere.)

Well, I can just do this:
"
import bitmaps
from bitmaps import EmulatedBitmap
"

and bitmaps.GROUPS makes it a little more obvious in-context at the
expense of one extra import line, so I'll do that.



  reply	other threads:[~2020-03-03 21:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-25  0:56 [PATCH 0/6] block: add block-dirty-bitmap-populate job John Snow
2020-02-25  0:56 ` [PATCH 1/6] block: add bitmap-populate job John Snow
2020-02-25 16:04   ` Vladimir Sementsov-Ogievskiy
2020-02-25 20:41     ` John Snow
2020-02-26  5:07       ` Vladimir Sementsov-Ogievskiy
2020-02-26 19:11         ` John Snow
2020-02-27  6:11           ` Vladimir Sementsov-Ogievskiy
2020-03-03 21:39             ` John Snow
2020-02-25  0:56 ` [PATCH 2/6] qmp: expose block-dirty-bitmap-populate John Snow
2020-02-27 10:44   ` Vladimir Sementsov-Ogievskiy
2020-03-03 21:48     ` John Snow
2020-02-25  0:56 ` [PATCH 3/6] iotests: move bitmap helpers into their own file John Snow
2020-02-27 10:54   ` Vladimir Sementsov-Ogievskiy
2020-03-03 21:55     ` John Snow [this message]
2020-02-25  0:56 ` [PATCH 4/6] iotests: add hmp helper with logging John Snow
2020-02-27 10:57   ` Vladimir Sementsov-Ogievskiy
2020-02-25  0:56 ` [PATCH 5/6] qmp.py: change event_wait to use a dict John Snow
2020-02-27 11:25   ` Vladimir Sementsov-Ogievskiy
2020-03-03 21:58     ` John Snow
2020-02-25  0:56 ` [PATCH 6/6] iotests: add 287 for block-dirty-bitmap-populate John Snow

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=65874958-de03-a7f3-ea20-914f38468a5d@redhat.com \
    --to=jsnow@redhat.com \
    --cc=armbru@redhat.com \
    --cc=crosa@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pkrempa@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vsementsov@virtuozzo.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.