public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Thomas Huth <thuth@redhat.com>, kvm@vger.kernel.org
Cc: 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>,
	Andrew Jones <drjones@redhat.com>
Subject: Re: [PATCH v3 0/3] KVM: selftests: Enable ucall and dirty_log_test on s390x
Date: Fri, 2 Aug 2019 15:39:31 +0200	[thread overview]
Message-ID: <551b42ae-78a1-e55a-e4b8-bb5cc3a8eb8b@de.ibm.com> (raw)
In-Reply-To: <20190731151525.17156-1-thuth@redhat.com>

On 31.07.19 17:15, Thomas Huth wrote:
> Implement the ucall() interface on s390x to be able to use the
> dirty_log_test KVM selftest on s390x, too.
> 
> v3:
>  - Fix compilation issue on aarch64 (thanks to Andrew for testing it!)
>  - Added Reviewed-bys
> 
> 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
>   KVM: selftests: Implement ucall() for s390x
>   KVM: selftests: Enable dirty_log_test on s390x
> 
>  tools/testing/selftests/kvm/Makefile          |   9 +-
>  tools/testing/selftests/kvm/dirty_log_test.c  |  61 ++++++-
>  .../testing/selftests/kvm/include/kvm_util.h  |   8 +-
>  .../testing/selftests/kvm/lib/aarch64/ucall.c | 112 +++++++++++++
>  tools/testing/selftests/kvm/lib/s390x/ucall.c |  56 +++++++
>  tools/testing/selftests/kvm/lib/ucall.c       | 157 ------------------
>  .../testing/selftests/kvm/lib/x86_64/ucall.c  |  56 +++++++
>  .../selftests/kvm/s390x/sync_regs_test.c      |   6 +-
>  8 files changed, 287 insertions(+), 178 deletions(-)
>  create mode 100644 tools/testing/selftests/kvm/lib/aarch64/ucall.c
>  create mode 100644 tools/testing/selftests/kvm/lib/s390x/ucall.c
>  delete mode 100644 tools/testing/selftests/kvm/lib/ucall.c
>  create mode 100644 tools/testing/selftests/kvm/lib/x86_64/ucall.c
> 

Paolo, I guess you do not mind if I carry patch 1 also via the s390x tree?

Thanks, all applied

  parent reply	other threads:[~2019-08-02 13:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31 15:15 [PATCH v3 0/3] KVM: selftests: Enable ucall and dirty_log_test on s390x Thomas Huth
2019-07-31 15:15 ` [PATCH v3 1/3] KVM: selftests: Split ucall.c into architecture specific files Thomas Huth
2019-07-31 15:15 ` [PATCH v3 2/3] KVM: selftests: Implement ucall() for s390x Thomas Huth
2019-07-31 15:15 ` [PATCH v3 3/3] KVM: selftests: Enable dirty_log_test on s390x Thomas Huth
2019-08-02 13:39 ` Christian Borntraeger [this message]
2019-08-02 13:43   ` [PATCH v3 0/3] KVM: selftests: Enable ucall and " Paolo Bonzini

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=551b42ae-78a1-e55a-e4b8-bb5cc3a8eb8b@de.ibm.com \
    --to=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 \
    --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