From: Thomas Huth <thuth@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Stephen Checkoway <s@pahtak.org>,
Stephen Checkoway <stephen.checkoway@oberlin.edu>,
qemu-block@nongnu.org, Laurent Vivier <lvivier@redhat.com>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 01/10] block/pflash_cfi02: Add test for supported commands
Date: Tue, 9 Apr 2019 10:40:14 +0200 [thread overview]
Message-ID: <17e16697-2f36-cdf3-4067-a04f5de6b66c@redhat.com> (raw)
In-Reply-To: <87tvf7d1a6.fsf@dusky.pond.sub.org>
On 09/04/2019 10.35, Markus Armbruster wrote:
> Thomas Huth <thuth@redhat.com> writes:
>
>> On 09/04/2019 09.45, Markus Armbruster wrote:
>>> Thomas Huth <thuth@redhat.com> writes:
>>>
>>>> We'd like to get rid of global_qtest in the long run (since it is
>>>> causing trouble for tests that run multiple instances of QEMU in
>>>> parallel, e.g. migration tests)... so if it is feasible, please don't
>>>> use it in new code anymore. Try to use a local variable in the function
>>>> that call qtest_initf() and pass the test state around via a parameter
>>>> to the functions that need it.
>>>
>>> Twenty tests still use @global_qtest
>>>
>>> Either we're serious about getting rid of @global_qtest. Then we should
>>> just do it.
>>
>> Ha ha, "just do it" ... that's quite a bit of work, actually. It's not
>> just about grep'ing for global_qtest, you also have to replace all the
>> writel(), readl() etc. functions with qtest_writel(), qtest_readl() etc.
>
> And that's precisely why I'm reluctant to demand this work from
> contributors. Asking nicely is of course fair.
That's what I did, didn't I? I said "... so if it is feasible, please
don't use it in new code anymore". I did not say "you must not use this
in new code anymore". So where's your problem here, Markus?
Stephen, for the records, in case my mail was not clear: I'm fine if you
keep the code as it currently is. But I'd be really happy if you could
change it to avoid global_qtest.
Thomas
next prev parent reply other threads:[~2019-04-09 8:40 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 20:55 [Qemu-devel] [PATCH 00/10] block/pflash_cfi02: Implement missing AMD pflash functionality Stephen Checkoway
2019-04-08 20:55 ` Stephen Checkoway
2019-04-08 20:55 ` [Qemu-devel] [PATCH 01/10] block/pflash_cfi02: Add test for supported commands Stephen Checkoway
2019-04-08 20:55 ` Stephen Checkoway
2019-04-09 6:13 ` Thomas Huth
2019-04-09 6:13 ` Thomas Huth
2019-04-09 7:45 ` Markus Armbruster
2019-04-09 7:45 ` Markus Armbruster
2019-04-09 8:16 ` Thomas Huth
2019-04-09 8:16 ` Thomas Huth
2019-04-09 8:35 ` Markus Armbruster
2019-04-09 8:35 ` Markus Armbruster
2019-04-09 8:40 ` Thomas Huth [this message]
2019-04-09 8:40 ` Thomas Huth
2019-04-09 8:50 ` Markus Armbruster
2019-04-09 8:50 ` Markus Armbruster
2019-04-09 15:37 ` Stephen Checkoway
2019-04-09 15:37 ` Stephen Checkoway
2019-04-10 14:39 ` Thomas Huth
2019-04-10 14:39 ` Thomas Huth
2019-04-08 20:55 ` [Qemu-devel] [PATCH 02/10] block/pflash_cfi02: Refactor, NFC intended Stephen Checkoway
2019-04-08 20:55 ` Stephen Checkoway
2019-04-08 20:55 ` [Qemu-devel] [PATCH 03/10] block/pflash_cfi02: Fix command address comparison Stephen Checkoway
2019-04-08 20:55 ` Stephen Checkoway
2019-04-08 20:55 ` [Qemu-devel] [PATCH 04/10] block/pflash_cfi02: Implement intereleaved flash devices Stephen Checkoway
2019-04-08 20:55 ` Stephen Checkoway
2019-04-08 20:55 ` [Qemu-devel] [PATCH 05/10] block/pflash_cfi02: Implement nonuniform sector sizes Stephen Checkoway
2019-04-08 20:55 ` Stephen Checkoway
2019-04-08 20:55 ` [Qemu-devel] [PATCH 06/10] block/pflash_cfi02: Fix CFI in autoselect mode Stephen Checkoway
2019-04-08 20:55 ` Stephen Checkoway
2019-04-08 20:55 ` [Qemu-devel] [PATCH 07/10] block/pflash_cfi02: Fix reset command not ignored during erase Stephen Checkoway
2019-04-08 20:55 ` Stephen Checkoway
2019-04-08 20:55 ` [Qemu-devel] [PATCH 08/10] block/pflash_cfi02: Implement multi-sector erase Stephen Checkoway
2019-04-08 20:55 ` Stephen Checkoway
2019-04-08 20:55 ` [Qemu-devel] [PATCH 09/10] block/pflash_cfi02: Implement erase suspend/resume Stephen Checkoway
2019-04-08 20:55 ` Stephen Checkoway
2019-04-08 20:55 ` [Qemu-devel] [PATCH 10/10] block/pflash_cfi02: Use the chip erase time specified in the CFI table Stephen Checkoway
2019-04-08 20:55 ` Stephen Checkoway
2019-04-08 21:11 ` [Qemu-devel] [PATCH 00/10] block/pflash_cfi02: Implement missing AMD pflash functionality no-reply
2019-04-08 21:11 ` no-reply
2019-04-09 10:34 ` Philippe Mathieu-Daudé
2019-04-09 10:34 ` Philippe Mathieu-Daudé
2019-04-09 15:55 ` Stephen Checkoway
2019-04-09 15:55 ` Stephen Checkoway
2019-04-09 16:15 ` Philippe Mathieu-Daudé
2019-04-09 16:15 ` Philippe Mathieu-Daudé
2019-04-09 18:00 ` Stephen Checkoway
2019-04-09 18:00 ` Stephen Checkoway
2019-04-18 21:00 ` Stephen Checkoway
2019-04-18 21:00 ` Stephen Checkoway
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=17e16697-2f36-cdf3-4067-a04f5de6b66c@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=lvivier@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=s@pahtak.org \
--cc=stephen.checkoway@oberlin.edu \
/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).