From: Janis Schoetterl-Glausch <scgl@linux.vnet.ibm.com>
To: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH v2 1/5] [kvm-unit-tests PATCH v2 0/5] Add specification exception tests
Date: Tue, 5 Oct 2021 13:14:16 +0200 [thread overview]
Message-ID: <a06c6df1-3da1-da43-3549-18f3abe6020d@linux.vnet.ibm.com> (raw)
In-Reply-To: <20211005090921.1816373-2-scgl@linux.ibm.com>
Oops, forgot to Cc the lists on the cover letter, see below.
Test that specification exceptions cause the correct interruption code
during both normal and transactional execution.
The last three patches are cosmetic only and could be dropped.
Unrelated: There should not be * in the file patterns in MAINTAINERS,
should there?
v1 -> v2
Add license and test description
Split test patch into normal test and transactional execution test
Add comments to
invalid PSW fixup function
with_transaction
Rename some variables/functions
Pass mask as single parameter to asm
Get rid of report_info_if macro
Introduce report_pass/fail and use them
Janis Schoetterl-Glausch (5):
s390x: Add specification exception test
s390x: Test specification exceptions during transaction
lib: Introduce report_pass and report_fail
Use report_fail(...) instead of report(0/false, ...)
Use report_pass(...) instead of report(1/true, ...)
s390x/Makefile | 1 +
lib/s390x/asm/arch_def.h | 1 +
lib/libcflat.h | 6 +-
lib/report.c | 20 ++-
lib/s390x/css_lib.c | 30 ++--
x86/vmx.h | 31 ++--
arm/psci.c | 2 +-
arm/timer.c | 2 +-
s390x/css.c | 22 +--
s390x/diag288.c | 2 +-
s390x/selftest.c | 2 +-
s390x/smp.c | 16 +-
s390x/spec_ex.c | 345 +++++++++++++++++++++++++++++++++++++++
x86/asyncpf.c | 11 +-
x86/emulator.c | 2 +-
x86/hyperv_stimer.c | 24 ++-
x86/hyperv_synic.c | 2 +-
x86/svm_tests.c | 180 ++++++++++----------
x86/syscall.c | 2 +-
x86/taskswitch2.c | 2 +-
x86/tsc_adjust.c | 2 +-
x86/vmx.c | 23 ++-
x86/vmx_tests.c | 172 ++++++++++---------
s390x/unittests.cfg | 3 +
24 files changed, 630 insertions(+), 273 deletions(-)
create mode 100644 s390x/spec_ex.c
base-commit: fe26131eec769cef7ad7e2e1e4e192aa0bdb2bba
--
2.31.1
next prev parent reply other threads:[~2021-10-05 11:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211005090921.1816373-1-scgl@linux.ibm.com>
2021-10-05 9:09 ` [kvm-unit-tests PATCH v2 1/5] s390x: Add specification exception test Janis Schoetterl-Glausch
2021-10-05 11:14 ` Janis Schoetterl-Glausch [this message]
[not found] ` <ef75d789-b613-e828-7d6d-2ab2b5e7618c@linux.ibm.com>
2021-10-05 13:32 ` Janis Schoetterl-Glausch
2021-10-05 14:51 ` Thomas Huth
2021-10-05 16:14 ` Janis Schoetterl-Glausch
2021-10-05 9:09 ` [kvm-unit-tests PATCH v2 2/5] s390x: Test specification exceptions during transaction Janis Schoetterl-Glausch
2021-10-05 9:09 ` [kvm-unit-tests PATCH v2 4/5] Use report_fail(...) instead of report(0/false, ...) Janis Schoetterl-Glausch
2021-10-05 11:53 ` Andrew Jones
2021-10-05 15:37 ` Thomas Huth
2021-10-05 9:09 ` [kvm-unit-tests PATCH v2 5/5] Use report_pass(...) instead of report(1/true, ...) Janis Schoetterl-Glausch
2021-10-05 15:42 ` Thomas Huth
2021-10-07 6:50 ` Thomas Huth
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=a06c6df1-3da1-da43-3549-18f3abe6020d@linux.vnet.ibm.com \
--to=scgl@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=scgl@linux.ibm.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