public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Morel <pmorel@linux.ibm.com>
To: linux-s390@vger.kernel.org
Cc: frankja@linux.ibm.com, thuth@redhat.com, kvm@vger.kernel.org,
	cohuck@redhat.com, imbrenda@linux.ibm.com, david@redhat.com,
	nrb@linux.ibm.com
Subject: [kvm-unit-tests PATCH 0/1] s390x: stsi: Define vm_is_kvm to be used in different tests
Date: Tue, 15 Feb 2022 11:46:31 +0100	[thread overview]
Message-ID: <20220215104632.47796-1-pmorel@linux.ibm.com> (raw)

Several tests are in need of a way to check on which hypervisor
and virtualization level they are running on to be able to fence
certain tests. This patch adds functions that return true if a
vm is running under KVM, LPAR or generally as a level 2 guest.
 
To check if we're running under KVM we use the STSI 3.2.2
instruction, let's define it's response structure in a central
header.

Pierre Morel (1):
  s390x: stsi: Define vm_is_kvm to be used in different tests

 lib/s390x/stsi.h | 32 ++++++++++++++++++++++++++++
 lib/s390x/vm.c   | 55 ++++++++++++++++++++++++++++++++++++++++++++++--
 lib/s390x/vm.h   |  3 +++
 s390x/stsi.c     | 23 ++------------------
 4 files changed, 90 insertions(+), 23 deletions(-)
 create mode 100644 lib/s390x/stsi.h

-- 
2.27.0


             reply	other threads:[~2022-02-15 10:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15 10:46 Pierre Morel [this message]
2022-02-15 10:46 ` [kvm-unit-tests PATCH 1/1] s390x: stsi: Define vm_is_kvm to be used in different tests Pierre Morel
2022-02-15 12:06   ` Claudio Imbrenda
2022-02-15 15:08     ` Janosch Frank
2022-02-15 15:21       ` Claudio Imbrenda
2022-02-15 17:30         ` Pierre Morel
2022-02-16  8:13           ` Janosch Frank
2022-02-16 12:26             ` Pierre Morel
2022-02-16 12:55               ` 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=20220215104632.47796-1-pmorel@linux.ibm.com \
    --to=pmorel@linux.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=nrb@linux.ibm.com \
    --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