From: Cornelia Huck <cohuck@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
"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: add a test for devices on s390x
Date: Fri, 27 Nov 2020 17:50:21 +0100 [thread overview]
Message-ID: <20201127175021.38a24e83.cohuck@redhat.com> (raw)
In-Reply-To: <20201126130158.1471985-1-cohuck@redhat.com>
On Thu, 26 Nov 2020 14:01:58 +0100
Cornelia Huck <cohuck@redhat.com> wrote:
> This adds a very basic test for checking that we present devices
> in a way that Linux can consume: boot with both virtio-net-ccw and
> virtio-net-pci attached and then verify that Linux is able to see
> and detect these devices.
>
> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> ---
> RFC->v2:
> - use a newer kernel that uses the uid in zpci address generation
> - add a zpci device to specify a uid
> - increase timeout
> - tweak naming
> - add a MAINTAINERS entry
> ---
> MAINTAINERS | 1 +
> tests/acceptance/machine_s390_ccw_virtio.py | 70 +++++++++++++++++++++
> 2 files changed, 71 insertions(+)
> create mode 100644 tests/acceptance/machine_s390_ccw_virtio.py
Queued to s390-next.
I plan to add some more stuff on top (like checking the mac address, or
adding more devices), but that will have to wait until next week.
next prev parent reply other threads:[~2020-11-27 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 13:01 [PATCH v2] tests/acceptance: add a test for devices on s390x Cornelia Huck
2020-11-26 13:16 ` Thomas Huth
2020-11-27 16:50 ` Cornelia Huck [this message]
2020-11-27 17:00 ` Wainer dos Santos Moschetta
2020-11-27 17:02 ` 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=20201127175021.38a24e83.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.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=thuth@redhat.com \
--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).