kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: thuth@redhat.com, borntraeger@de.ibm.com, david@redhat.com,
	cohuck@redhat.com, linux-s390@vger.kernel.org
Subject: [PATCH v10 0/6] KVM: s390: Add new reset vcpu API
Date: Fri, 31 Jan 2020 05:01:59 -0500	[thread overview]
Message-ID: <20200131100205.74720-1-frankja@linux.ibm.com> (raw)

Let's implement the remaining resets, namely the normal and clear
reset to improve architectural compliance.

While we're at it, let's also start testing the new API.
Those tests are not yet complete, but will be extended in the future.

v10:
	* Cleared up the test patch and added strerror information
	* Removed capability checks from irq test
	* Fixed clobber patch

Christian Borntraeger (1):
  KVM: s390: do not clobber registers during guest reset/store status

Janosch Frank (4):
  KVM: s390: Cleanup initial cpu reset
  KVM: s390: Add new reset vcpu API
  selftests: KVM: Add fpu and one reg set/get library functions
  selftests: KVM: s390x: Add reset tests

Pierre Morel (1):
  selftests: KVM: testing the local IRQs resets

 Documentation/virt/kvm/api.txt                |  43 ++++
 arch/s390/include/asm/kvm_host.h              |   5 +
 arch/s390/kvm/kvm-s390.c                      |  92 +++++---
 include/uapi/linux/kvm.h                      |   5 +
 tools/testing/selftests/kvm/Makefile          |   1 +
 .../testing/selftests/kvm/include/kvm_util.h  |   6 +
 tools/testing/selftests/kvm/lib/kvm_util.c    |  36 ++++
 tools/testing/selftests/kvm/s390x/resets.c    | 197 ++++++++++++++++++
 8 files changed, 351 insertions(+), 34 deletions(-)
 create mode 100644 tools/testing/selftests/kvm/s390x/resets.c

-- 
2.20.1


             reply	other threads:[~2020-01-31 10:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-31 10:01 Janosch Frank [this message]
2020-01-31 10:02 ` [PATCH v10 1/6] KVM: s390: do not clobber registers during guest reset/store status Janosch Frank
2020-01-31 11:24   ` Christian Borntraeger
2020-01-31 10:02 ` [PATCH v10 2/6] KVM: s390: Cleanup initial cpu reset Janosch Frank
2020-01-31 11:31   ` Christian Borntraeger
2020-01-31 10:02 ` [PATCH v10 3/6] KVM: s390: Add new reset vcpu API Janosch Frank
2020-01-31 11:44   ` Thomas Huth
2020-01-31 11:50   ` Christian Borntraeger
2020-01-31 10:02 ` [PATCH v10 4/6] selftests: KVM: Add fpu and one reg set/get library functions Janosch Frank
2020-01-31 11:43   ` Christian Borntraeger
2020-01-31 13:59     ` Paolo Bonzini
2020-01-31 12:18   ` Christian Borntraeger
2020-01-31 10:02 ` [PATCH v10 5/6] selftests: KVM: s390x: Add reset tests Janosch Frank
2020-01-31 12:18   ` Christian Borntraeger
2020-01-31 10:02 ` [PATCH v10 6/6] selftests: KVM: testing the local IRQs resets Janosch Frank
2020-01-31 10:16   ` Cornelia Huck
2020-01-31 11:47   ` Thomas Huth
2020-01-31 12:47   ` Christian Borntraeger

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=20200131100205.74720-1-frankja@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.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;
as well as URLs for NNTP newsgroup(s).