Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: thuth at redhat.com (Thomas Huth)
Subject: [RFC PATCH 0/4] KVM selftests for s390x
Date: Thu, 16 May 2019 13:12:49 +0200	[thread overview]
Message-ID: <20190516111253.4494-1-thuth@redhat.com> (raw)

This patch series enables the KVM selftests for s390x. As a first
test, the sync_regs from x86 has been adapted to s390x.

Please note that the ucall() interface is not used yet - since
s390x neither has PIO nor MMIO, this needs some more work first
before it becomes usable (we likely should use a DIAG hypercall
here, which is what the sync_reg test is currently using, too...).

Thomas Huth (4):
  KVM: selftests: Guard struct kvm_vcpu_events with
    __KVM_HAVE_VCPU_EVENTS
  KVM: selftests: Align memory region addresses to 1M on s390x
  KVM: selftests: Add processor code for s390x
  KVM: selftests: Add the sync_regs test for s390x

 MAINTAINERS                                   |   2 +
 tools/testing/selftests/kvm/Makefile          |   3 +
 .../testing/selftests/kvm/include/kvm_util.h  |   2 +
 .../selftests/kvm/include/s390x/processor.h   |  22 ++
 tools/testing/selftests/kvm/lib/kvm_util.c    |  24 +-
 .../selftests/kvm/lib/s390x/processor.c       | 277 ++++++++++++++++++
 .../selftests/kvm/s390x/sync_regs_test.c      | 151 ++++++++++
 7 files changed, 476 insertions(+), 5 deletions(-)
 create mode 100644 tools/testing/selftests/kvm/include/s390x/processor.h
 create mode 100644 tools/testing/selftests/kvm/lib/s390x/processor.c
 create mode 100644 tools/testing/selftests/kvm/s390x/sync_regs_test.c

-- 
2.21.0

WARNING: multiple messages have this Message-ID (diff)
From: thuth@redhat.com (Thomas Huth)
Subject: [RFC PATCH 0/4] KVM selftests for s390x
Date: Thu, 16 May 2019 13:12:49 +0200	[thread overview]
Message-ID: <20190516111253.4494-1-thuth@redhat.com> (raw)
Message-ID: <20190516111249.gOXWXmzQlQ_woqkvL6mdbKuygYdP6zpX-xJvyNc4UGE@z> (raw)

This patch series enables the KVM selftests for s390x. As a first
test, the sync_regs from x86 has been adapted to s390x.

Please note that the ucall() interface is not used yet - since
s390x neither has PIO nor MMIO, this needs some more work first
before it becomes usable (we likely should use a DIAG hypercall
here, which is what the sync_reg test is currently using, too...).

Thomas Huth (4):
  KVM: selftests: Guard struct kvm_vcpu_events with
    __KVM_HAVE_VCPU_EVENTS
  KVM: selftests: Align memory region addresses to 1M on s390x
  KVM: selftests: Add processor code for s390x
  KVM: selftests: Add the sync_regs test for s390x

 MAINTAINERS                                   |   2 +
 tools/testing/selftests/kvm/Makefile          |   3 +
 .../testing/selftests/kvm/include/kvm_util.h  |   2 +
 .../selftests/kvm/include/s390x/processor.h   |  22 ++
 tools/testing/selftests/kvm/lib/kvm_util.c    |  24 +-
 .../selftests/kvm/lib/s390x/processor.c       | 277 ++++++++++++++++++
 .../selftests/kvm/s390x/sync_regs_test.c      | 151 ++++++++++
 7 files changed, 476 insertions(+), 5 deletions(-)
 create mode 100644 tools/testing/selftests/kvm/include/s390x/processor.h
 create mode 100644 tools/testing/selftests/kvm/lib/s390x/processor.c
 create mode 100644 tools/testing/selftests/kvm/s390x/sync_regs_test.c

-- 
2.21.0

             reply	other threads:[~2019-05-16 11:12 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16 11:12 thuth [this message]
2019-05-16 11:12 ` [RFC PATCH 0/4] KVM selftests for s390x Thomas Huth
2019-05-16 11:12 ` [RFC PATCH 1/4] KVM: selftests: Guard struct kvm_vcpu_events with __KVM_HAVE_VCPU_EVENTS thuth
2019-05-16 11:12   ` Thomas Huth
2019-05-16 11:22   ` david
2019-05-16 11:22     ` David Hildenbrand
2019-05-20  7:12   ` borntraeger
2019-05-20  7:12     ` Christian Borntraeger
2019-05-20  8:08     ` thuth
2019-05-20  8:08       ` Thomas Huth
2019-05-20  8:13       ` borntraeger
2019-05-20  8:13         ` Christian Borntraeger
2019-05-16 11:12 ` [RFC PATCH 2/4] KVM: selftests: Align memory region addresses to 1M on s390x thuth
2019-05-16 11:12   ` Thomas Huth
2019-05-16 11:30   ` david
2019-05-16 11:30     ` David Hildenbrand
2019-05-16 11:59     ` thuth
2019-05-16 11:59       ` Thomas Huth
2019-05-16 12:08       ` david
2019-05-16 12:08         ` David Hildenbrand
2019-05-16 11:12 ` [RFC PATCH 3/4] KVM: selftests: Add processor code for s390x thuth
2019-05-16 11:12   ` Thomas Huth
2019-05-16 11:12 ` [RFC PATCH 4/4] KVM: selftests: Add the sync_regs test " thuth
2019-05-16 11:12   ` Thomas Huth
2019-05-20 11:19   ` pbonzini
2019-05-20 11:19     ` Paolo Bonzini
2019-05-23 10:56   ` drjones
2019-05-23 10:56     ` Andrew Jones
2019-05-23 11:19     ` thuth
2019-05-23 11:19       ` Thomas Huth
2019-05-20 11:20 ` [RFC PATCH 0/4] KVM selftests " pbonzini
2019-05-20 11:20   ` Paolo Bonzini
2019-05-20 11:30   ` thuth
2019-05-20 11:30     ` Thomas Huth
2019-05-20 11:43     ` pbonzini
2019-05-20 11:43       ` Paolo Bonzini
2019-05-22  8:44       ` drjones
2019-05-22  8:44         ` Andrew Jones

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=20190516111253.4494-1-thuth@redhat.com \
    --to=linux-kselftest@vger.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