From: Wainer dos Santos Moschetta <wainersm@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, Cornelia Huck <cohuck@redhat.com>
Cc: qemu-s390x@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>
Subject: Re: [PATCH 2/3] tests/acceptance/machine_s390_ccw_virtio: Test virtio-rng via /dev/hwrng
Date: Fri, 11 Dec 2020 17:30:24 -0300 [thread overview]
Message-ID: <7f2adbee-49e0-94f7-fcd7-7e012cc36bfa@redhat.com> (raw)
In-Reply-To: <20201211173134.376078-3-thuth@redhat.com>
Hi,
On 12/11/20 2:31 PM, Thomas Huth wrote:
> /dev/hwrng is only functional if virtio-rng is working right, so let's
> add a sanity check for this device node.
Good idea.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> tests/acceptance/machine_s390_ccw_virtio.py | 17 +++++++++++++++--
> 1 file changed, 15 insertions(+), 2 deletions(-)
>
> diff --git a/tests/acceptance/machine_s390_ccw_virtio.py b/tests/acceptance/machine_s390_ccw_virtio.py
> index 733a7ca24a..7d0a78139b 100644
> --- a/tests/acceptance/machine_s390_ccw_virtio.py
> +++ b/tests/acceptance/machine_s390_ccw_virtio.py
> @@ -64,9 +64,9 @@ class S390CCWVirtioMachine(Test):
> '-append', kernel_command_line,
> '-device', 'virtio-net-ccw,devno=fe.1.1111',
> '-device',
> - 'virtio-rng-ccw,devno=fe.2.0000,max_revision=0',
> + 'virtio-rng-ccw,devno=fe.2.0000,max_revision=0,id=rn1',
> '-device',
> - 'virtio-rng-ccw,devno=fe.3.1234,max_revision=2',
> + 'virtio-rng-ccw,devno=fe.3.1234,max_revision=2,id=rn2',
> '-device', 'zpci,uid=5,target=zzz',
> '-device', 'virtio-net-pci,id=zzz',
> '-device', 'zpci,uid=0xa,fid=12,target=serial',
> @@ -96,6 +96,19 @@ class S390CCWVirtioMachine(Test):
> exec_command_and_wait_for_pattern(self,
> 'cat /sys/bus/ccw/devices/0.3.1234/virtio?/features',
> virtio_rng_features)
> + # check that /dev/hwrng works - and that it's gone after ejecting
> + exec_command_and_wait_for_pattern(self,
> + 'dd if=/dev/hwrng of=/tmp/out.dat bs=1k count=10',
> + '10+0 records out')
> + self.clear_guests_dmesg()
> + self.vm.command('device_del', id='rn1')
> + self.wait_for_crw_reports()
> + self.clear_guests_dmesg()
> + self.vm.command('device_del', id='rn2')
> + self.wait_for_crw_reports()
> + exec_command_and_wait_for_pattern(self,
> + 'dd if=/dev/hwrng of=/tmp/out.dat bs=1k count=10',
> + 'dd: /dev/hwrng: No such device')
Maybe the expected pattern is too fragile. On my Fedora 33 system, 'dd'
will print a different message.
What if it checks for the presence of the device file, e.g:
... self, 'test -c /dev/hwrng; echo $?', '1')
- Wainer
> # verify that we indeed have virtio-net devices (without having the
> # virtio-net driver handy)
> exec_command_and_wait_for_pattern(self,
next prev parent reply other threads:[~2020-12-11 20:35 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 [this message]
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
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=7f2adbee-49e0-94f7-fcd7-7e012cc36bfa@redhat.com \
--to=wainersm@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=thuth@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).