From: Janosch Frank <frankja@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: thuth@redhat.com, linux-s390@vger.kernel.org, david@redhat.com,
borntraeger@de.ibm.com, cohuck@redhat.com,
imbrenda@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH v2 0/3] PV tests part 1
Date: Tue, 11 Aug 2020 09:29:12 +0200 [thread overview]
Message-ID: <8ba7de43-8195-9492-e973-1474cd75933c@linux.ibm.com> (raw)
In-Reply-To: <20200807111555.11169-1-frankja@linux.ibm.com>
[-- Attachment #1.1: Type: text/plain, Size: 1510 bytes --]
On 8/7/20 1:15 PM, Janosch Frank wrote:
> Let's start bringing in some more PV related code.
>
> Somehow I missed that we can also have a key in a exception new
> PSW. The interesting bit is that if such a PSW is loaded on an
> exception it will result in a specification exception and not a
> special operation exception.
>
> The third patch adds a basic guest UV call API test. It has mostly
> been used for firmware testing but I also think it's good to have a
> building block like this for more PV tests.
>
>
> GIT: https://gitlab.com/frankja/kvm-unit-tests/-/tree/queue
Picked the series onto:
https://gitlab.com/frankja/kvm-unit-tests/-/commits/next
>
>
> v2:
> * Renamed pgm_int_func to pgm_cleanup_func() and moved the call to handle_pgm_int()
> * Added page allocation to UV test
> * Cleanups
>
> Janosch Frank (3):
> s390x: Add custom pgm cleanup function
> s390x: skrf: Add exception new skey test and add test to unittests.cfg
> s390x: Ultravisor guest API test
>
> lib/s390x/asm/interrupt.h | 1 +
> lib/s390x/asm/uv.h | 74 +++++++++++++++++
> lib/s390x/interrupt.c | 12 ++-
> s390x/Makefile | 1 +
> s390x/skrf.c | 79 +++++++++++++++++++
> s390x/unittests.cfg | 7 ++
> s390x/uv-guest.c | 162 ++++++++++++++++++++++++++++++++++++++
> 7 files changed, 335 insertions(+), 1 deletion(-)
> create mode 100644 lib/s390x/asm/uv.h
> create mode 100644 s390x/uv-guest.c
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-08-11 7:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 11:15 [kvm-unit-tests PATCH v2 0/3] PV tests part 1 Janosch Frank
2020-08-07 11:15 ` [kvm-unit-tests PATCH v2 1/3] s390x: Add custom pgm cleanup function Janosch Frank
2020-08-10 12:21 ` Cornelia Huck
2020-08-07 11:15 ` [kvm-unit-tests PATCH v2 2/3] s390x: skrf: Add exception new skey test and add test to unittests.cfg Janosch Frank
2020-08-07 12:12 ` Thomas Huth
2020-08-10 14:38 ` Cornelia Huck
2020-08-07 11:15 ` [kvm-unit-tests PATCH v2 3/3] s390x: Ultravisor guest API test Janosch Frank
2020-08-07 12:14 ` Thomas Huth
2020-08-10 14:50 ` Cornelia Huck
2020-08-10 15:27 ` Janosch Frank
2020-08-10 15:32 ` Cornelia Huck
2020-08-10 15:45 ` [kvm-unit-tests PATCH v3] " Janosch Frank
2020-08-10 15:50 ` Cornelia Huck
2020-08-11 7:18 ` Janosch Frank
2020-08-11 7:29 ` Janosch Frank [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-27 9:54 [kvm-unit-tests PATCH v2 0/3] PV tests part 1 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=8ba7de43-8195-9492-e973-1474cd75933c@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.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