From: Steffen Eiden <seiden@linux.ibm.com>
To: linux-s390@vger.kernel.org
Cc: Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Shuah Khan <shuah@kernel.org>, Nico Boehr <nrb@linux.ibm.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: [PATCH v3 4/4] selftests: drivers/s390x: Add uvdevice QUI tests
Date: Fri, 4 Mar 2022 09:11:41 -0500 [thread overview]
Message-ID: <20220304141141.32767-5-seiden@linux.ibm.com> (raw)
In-Reply-To: <20220304141141.32767-1-seiden@linux.ibm.com>
Add test variant to also verify that QUI-error paths
are working as intended.
./test-uv-device
TAP version 13
1..10
# Starting 10 tests from 4 test cases.
# RUN uvio_fixture.qui.fault_ioctl_arg ...
# OK uvio_fixture.qui.fault_ioctl_arg
ok 1 uvio_fixture.qui.fault_ioctl_arg
# RUN uvio_fixture.qui.fault_uvio_arg ...
# OK uvio_fixture.qui.fault_uvio_arg
ok 2 uvio_fixture.qui.fault_uvio_arg
# RUN uvio_fixture.qui.inval_ioctl_cb ...
# OK uvio_fixture.qui.inval_ioctl_cb
ok 3 uvio_fixture.qui.inval_ioctl_cb
# RUN uvio_fixture.qui.inval_ioctl_cmd ...
# OK uvio_fixture.qui.inval_ioctl_cmd
ok 4 uvio_fixture.qui.inval_ioctl_cmd
# RUN uvio_fixture.att.fault_ioctl_arg ...
# OK uvio_fixture.att.fault_ioctl_arg
ok 5 uvio_fixture.att.fault_ioctl_arg
# RUN uvio_fixture.att.fault_uvio_arg ...
# OK uvio_fixture.att.fault_uvio_arg
ok 6 uvio_fixture.att.fault_uvio_arg
# RUN uvio_fixture.att.inval_ioctl_cb ...
# OK uvio_fixture.att.inval_ioctl_cb
ok 7 uvio_fixture.att.inval_ioctl_cb
# RUN uvio_fixture.att.inval_ioctl_cmd ...
# OK uvio_fixture.att.inval_ioctl_cmd
ok 8 uvio_fixture.att.inval_ioctl_cmd
# RUN attest_fixture.att_inval_request ...
# OK attest_fixture.att_inval_request
ok 9 attest_fixture.att_inval_request
# RUN attest_fixture.att_inval_addr ...
# OK attest_fixture.att_inval_addr
ok 10 attest_fixture.att_inval_addr
# PASSED: 10 / 10 tests passed.
# Totals: pass:10 fail:0 xfail:0 xpass:0 skip:0 error:0
Signed-off-by: Steffen Eiden <seiden@linux.ibm.com>
Acked-by: Janosch Frank <frankja@linux.ibm.com>
---
.../testing/selftests/drivers/s390x/uvdevice/test_uvdevice.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/tools/testing/selftests/drivers/s390x/uvdevice/test_uvdevice.c b/tools/testing/selftests/drivers/s390x/uvdevice/test_uvdevice.c
index ea0cdc37b44f..44a6fbefc156 100644
--- a/tools/testing/selftests/drivers/s390x/uvdevice/test_uvdevice.c
+++ b/tools/testing/selftests/drivers/s390x/uvdevice/test_uvdevice.c
@@ -30,6 +30,11 @@ FIXTURE_VARIANT(uvio_fixture) {
uint32_t arg_size;
};
+FIXTURE_VARIANT_ADD(uvio_fixture, qui) {
+ .ioctl_cmd = UVIO_IOCTL_QUI,
+ .arg_size = BUFFER_SIZE,
+};
+
FIXTURE_VARIANT_ADD(uvio_fixture, att) {
.ioctl_cmd = UVIO_IOCTL_ATT,
.arg_size = sizeof(struct uvio_attest),
--
2.25.1
next prev parent reply other threads:[~2022-03-04 14:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 14:11 [PATCH v3 0/4] s390: Ultravisor device Steffen Eiden
2022-03-04 14:11 ` [PATCH v3 1/4] drivers/s390/char: Add Ultravisor io device Steffen Eiden
2022-03-16 8:23 ` Janosch Frank
2022-03-16 9:02 ` Janosch Frank
2022-03-17 9:47 ` [PATCH v3 1/4] drivers/s390/char: Add Ultravisor io device' Steffen Eiden
2022-03-17 9:59 ` Greg KH
2022-03-17 11:07 ` [PATCH v3 1/4] drivers/s390/char: Add Ultravisor io device Steffen Eiden
2022-03-17 11:23 ` Steffen Eiden
2022-03-17 11:59 ` Greg KH
2022-03-04 14:11 ` [PATCH v3 2/4] drivers/s390/char: Add Query Ultravisor Information to uvdevice Steffen Eiden
2022-03-16 8:56 ` Janosch Frank
2022-03-04 14:11 ` [PATCH v3 3/4] selftests: drivers/s390x: Add uvdevice tests Steffen Eiden
2022-03-04 14:11 ` Steffen Eiden [this message]
2022-03-16 9:04 ` [PATCH v3 0/4] s390: Ultravisor device Janosch Frank
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=20220304141141.32767-5-seiden@linux.ibm.com \
--to=seiden@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=shuah@kernel.org \
/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