qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>, qemu-devel@nongnu.org
Cc: "Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Halil Pasic" <pasic@linux.ibm.com>,
	"Christian Borntraeger" <borntraeger@de.ibm.com>,
	qemu-s390x@nongnu.org, "Cleber Rosa" <crosa@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v2] tests/acceptance: test hot(un)plug of ccw devices
Date: Mon, 7 Dec 2020 15:28:47 +0100	[thread overview]
Message-ID: <c3c60abd-2a38-8267-aafa-9a7534d5bf24@redhat.com> (raw)
In-Reply-To: <20201204121450.120730-1-cohuck@redhat.com>

On 04/12/2020 13.14, Cornelia Huck wrote:
> Hotplug a virtio-net-ccw device, and then hotunplug it again.
> 
> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> ---
> 
> v1->v2:
> - switch device id
> - clear out dmesg before looking for CRW messages
> 
> ---
>  tests/acceptance/machine_s390_ccw_virtio.py | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
> 
> diff --git a/tests/acceptance/machine_s390_ccw_virtio.py b/tests/acceptance/machine_s390_ccw_virtio.py
> index 53b8484f8f9c..83c00190621b 100644
> --- a/tests/acceptance/machine_s390_ccw_virtio.py
> +++ b/tests/acceptance/machine_s390_ccw_virtio.py
> @@ -97,3 +97,19 @@ class S390CCWVirtioMachine(Test):
>          exec_command_and_wait_for_pattern(self,
>                                            'cat /sys/bus/pci/devices/000a\:00\:00.0/function_id',
>                                            '0x0000000c')
> +        # add another device
> +        exec_command_and_wait_for_pattern(self, 'dmesg -c', ' ')
> +        self.vm.command('device_add', driver='virtio-net-ccw',
> +                        devno='fe.0.4711', id='net_4711')
> +        exec_command_and_wait_for_pattern(self, 'dmesg', 'CRW')

Looking at this twice, I'm a little bit afraid that this could be racy -
what if the kernel decides to emit the line with the "CRW" just after we
executed the dmesg command? I'd maybe use something like this instead:

exec_command_and_wait_for_pattern(self,
 'while ! dmesg -c | grep CRW ; do sleep 1 ; done', '~ #')

> +        exec_command_and_wait_for_pattern(self, 'ls /sys/bus/ccw/devices/',
> +                                          '0.0.4711')
> +        # and detach it again
> +        exec_command_and_wait_for_pattern(self, 'dmesg -c', ' ')

If adapt my above change, you could also get rid of this dmesg -c here
(since it's done in the while loop already)

> +        self.vm.command('device_del', id='net_4711')
> +        self.vm.event_wait(name='DEVICE_DELETED',
> +                           match={'data': {'device': 'net_4711'}})
> +        exec_command_and_wait_for_pattern(self, 'dmesg', 'CRW')

dito

> +        exec_command_and_wait_for_pattern(self,
> +                                          'ls /sys/bus/ccw/devices/0.0.4711',
> +                                          'No such file or directory')

With my suggestion applied:

Reviewed-by: Thomas Huth <thuth@redhat.com>



  parent reply	other threads:[~2020-12-07 14:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04 12:14 [PATCH v2] tests/acceptance: test hot(un)plug of ccw devices Cornelia Huck
2020-12-04 14:05 ` Wainer dos Santos Moschetta
2020-12-04 14:08   ` Cornelia Huck
2020-12-04 20:13     ` Wainer dos Santos Moschetta
2020-12-07 11:12       ` Cornelia Huck
2020-12-07 14:28 ` Thomas Huth [this message]
2020-12-07 16:30   ` Cornelia Huck
2020-12-07 16:34     ` Thomas Huth
2020-12-07 18:40       ` Thomas Huth
2020-12-08 11:43         ` Cornelia Huck

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=c3c60abd-2a38-8267-aafa-9a7534d5bf24@redhat.com \
    --to=thuth@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=crosa@redhat.com \
    --cc=pasic@linux.ibm.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=wainersm@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).