From: pbonzini at redhat.com (Paolo Bonzini)
Subject: [RFC PATCH 0/4] KVM selftests for s390x
Date: Mon, 20 May 2019 13:20:03 +0200 [thread overview]
Message-ID: <b412e591-3983-ebef-510b-43f9b7be4147@redhat.com> (raw)
In-Reply-To: <20190516111253.4494-1-thuth@redhat.com>
On 16/05/19 13:12, Thomas Huth wrote:
> 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...).
No objections at all, though it would be like to have ucall plumbed in
from the beginning.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: pbonzini@redhat.com (Paolo Bonzini)
Subject: [RFC PATCH 0/4] KVM selftests for s390x
Date: Mon, 20 May 2019 13:20:03 +0200 [thread overview]
Message-ID: <b412e591-3983-ebef-510b-43f9b7be4147@redhat.com> (raw)
Message-ID: <20190520112003.x7PebC2k3VJc9bHkmdEdsE3SwmYTw3ev-xEmtdSqBTg@z> (raw)
In-Reply-To: <20190516111253.4494-1-thuth@redhat.com>
On 16/05/19 13:12, Thomas Huth wrote:
> 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...).
No objections at all, though it would be like to have ucall plumbed in
from the beginning.
Paolo
next prev parent reply other threads:[~2019-05-20 11:20 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 11:12 [RFC PATCH 0/4] KVM selftests for s390x thuth
2019-05-16 11:12 ` 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 ` pbonzini [this message]
2019-05-20 11:20 ` [RFC PATCH 0/4] KVM selftests " 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=b412e591-3983-ebef-510b-43f9b7be4147@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