From: Thomas Huth <thuth@redhat.com>
To: kvm@vger.kernel.org, Andrew Jones <drjones@redhat.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-s390@vger.kernel.org, David Hildenbrand <david@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>, Peter Xu <peterx@redhat.com>
Subject: Re: [PATCH v2 0/3] KVM: selftests: Enable ucall and dirty_log_test on s390x
Date: Wed, 31 Jul 2019 15:39:40 +0200 [thread overview]
Message-ID: <9a2d3e3c-67f1-d53b-944e-5f3b6a1fc8b0@redhat.com> (raw)
In-Reply-To: <20190731133216.5620-1-thuth@redhat.com>
On 31/07/2019 15.32, Thomas Huth wrote:
> Implement the ucall() interface on s390x to be able to use the
> dirty_log_test KVM selftest on s390x, too.
>
> v2:
> - Split up ucall.c into architecture specific files
> - Removed some #ifdef __s390x__ in the dirty_log patch
>
> Thomas Huth (3):
> KVM: selftests: Split ucall.c into architecture specific files
I forgot to say: I only checked x86 and s390x ... Andrew, could you
please check that the dirty_log_test still builds and runs fine on
aarch64 after applying my patches? (Sorry, I tried to get a aarch64
machine here, but so far I failed...)
Thanks,
Thomas
next prev parent reply other threads:[~2019-07-31 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 13:32 [PATCH v2 0/3] KVM: selftests: Enable ucall and dirty_log_test on s390x Thomas Huth
2019-07-31 13:32 ` [PATCH v2 1/3] KVM: selftests: Split ucall.c into architecture specific files Thomas Huth
2019-07-31 14:43 ` Andrew Jones
2019-07-31 13:32 ` [PATCH v2 2/3] KVM: selftests: Implement ucall() for s390x Thomas Huth
2019-07-31 13:32 ` [PATCH v2 3/3] KVM: selftests: Enable dirty_log_test on s390x Thomas Huth
2019-07-31 13:39 ` Thomas Huth [this message]
2019-07-31 14:51 ` [PATCH v2 0/3] KVM: selftests: Enable ucall and " 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=9a2d3e3c-67f1-d53b-944e-5f3b6a1fc8b0@redhat.com \
--to=thuth@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=drjones@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterx@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).