From: Thomas Huth <thuth@redhat.com>
To: Willian Rampazzo <wrampazz@redhat.com>,
qemu-devel@nongnu.org, Cornelia Huck <cohuck@redhat.com>
Cc: qemu-s390x@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>
Subject: Re: [PATCH 0/3] tests/acceptance: Test virtio-rng and -balloon on s390x
Date: Sat, 12 Dec 2020 08:15:13 +0100 [thread overview]
Message-ID: <ee0257d8-3b38-5baf-5552-8c0f3f09ce37@redhat.com> (raw)
In-Reply-To: <15276695-1718-e3a9-907e-c6e145294a87@redhat.com>
On 11/12/2020 21.10, Willian Rampazzo wrote:
> On 12/11/20 2:31 PM, Thomas Huth wrote:
>> Add two more simple tests to check that virtio-rng and virtio-balloon
>> are at least (very) basically working on s390x.
>>
>> Based-on: 20201204121450.120730-1-cohuck@redhat.com
>>
>> Thomas Huth (3):
>> tests/acceptance: Extract the code to clear dmesg and wait for CRW
>> reports
>> tests/acceptance/machine_s390_ccw_virtio: Test virtio-rng via
>> /dev/hwrng
>> tests/acceptance/machine_s390_ccw_virtio: Test the virtio-balloon
>> device
>>
>> tests/acceptance/machine_s390_ccw_virtio.py | 59 +++++++++++++++------
>> 1 file changed, 43 insertions(+), 16 deletions(-)
>>
>
> One observation, test_s390x_devices tends to get longer and difficult to
> debug in case of problems. If a test covers one specific device type, It
> will improve readability, flexibility, and debugging. In case you don't want
> to spend time breaking this into multiple tests, I'll be glad to do that
> after the whole series is merged.
Theoretically yes, but practically we also want to run the tests as fast as
possible. Quite a bit of time is used to boot the kernel, so if we add a new
test for each and every device, that would increase the test time quite a
bit. Thus I'd rather prefer to keep everything in one single test instead
for now.
> As far as code concerned,
>
> Reviewed-by: Willian Rampazzo <willianr@redhat.com>
> Tested-by: Willian Rampazzo <willianr@redhat.com>
Thanks!
Thomas
next prev parent reply other threads:[~2020-12-12 7:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 17:31 [PATCH 0/3] tests/acceptance: Test virtio-rng and -balloon on s390x Thomas Huth
2020-12-11 17:31 ` [PATCH 1/3] tests/acceptance: Extract the code to clear dmesg and wait for CRW reports Thomas Huth
2020-12-11 20:10 ` Wainer dos Santos Moschetta
2020-12-14 12:26 ` Cornelia Huck
2020-12-11 17:31 ` [PATCH 2/3] tests/acceptance/machine_s390_ccw_virtio: Test virtio-rng via /dev/hwrng Thomas Huth
2020-12-11 20:30 ` Wainer dos Santos Moschetta
2020-12-12 7:10 ` Thomas Huth
2020-12-14 13:00 ` Cornelia Huck
2020-12-15 14:30 ` Wainer dos Santos Moschetta
2020-12-11 17:31 ` [PATCH 3/3] tests/acceptance/machine_s390_ccw_virtio: Test the virtio-balloon device Thomas Huth
2020-12-11 20:42 ` Wainer dos Santos Moschetta
2020-12-11 20:10 ` [PATCH 0/3] tests/acceptance: Test virtio-rng and -balloon on s390x Willian Rampazzo
2020-12-12 7:15 ` Thomas Huth [this message]
2020-12-14 11:39 ` Cornelia Huck
2020-12-14 15:14 ` Willian Rampazzo
2020-12-14 15:12 ` Willian Rampazzo
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=ee0257d8-3b38-5baf-5552-8c0f3f09ce37@redhat.com \
--to=thuth@redhat.com \
--cc=cohuck@redhat.com \
--cc=crosa@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=wainersm@redhat.com \
--cc=wrampazz@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).