Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: Alexander Gordeev <agordeev@linux.ibm.com>,
	David Hildenbrand <david@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	linux-kselftest@vger.kernel.org,
	Janosch Frank <frankja@linux.ibm.com>,
	Claudio Imbrenda <imbrenda@linux.ibm.com>,
	Thomas Huth <thuth@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH v1] KVM: s390x: selftests: Add shared zeropage test
Date: Mon, 15 Apr 2024 16:27:14 +0200	[thread overview]
Message-ID: <743bd638-2a9d-4c53-bc44-14292edef58a@linux.ibm.com> (raw)
In-Reply-To: <Zh03fI2oA0UkE0Kp@tuxmaker.boeblingen.de.ibm.com>



Am 15.04.24 um 16:19 schrieb Alexander Gordeev:
> On Fri, Apr 12, 2024 at 10:43:29AM +0200, David Hildenbrand wrote:
> Hi David,
>>   tools/testing/selftests/kvm/Makefile          |   1 +
>>   .../kvm/s390x/shared_zeropage_test.c          | 110 ++++++++++++++++++
>>   2 files changed, 111 insertions(+)
>>   create mode 100644 tools/testing/selftests/kvm/s390x/shared_zeropage_test.c
> 
> Tested-by: Alexander Gordeev <agordeev@linux.ibm.com>
> 
> @Janosch, Christian,
> 
> I think this patch should go via s390 tree together with
> https://lore.kernel.org/r/20240411161441.910170-3-david@redhat.com
> 
> Do you agree?

Yes, thank you

Acked-by: Christian Borntraeger <borntraeger@linux.ibm.com>

  parent reply	other threads:[~2024-04-15 14:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12  8:43 [PATCH v1] KVM: s390x: selftests: Add shared zeropage test David Hildenbrand
2024-04-15 14:19 ` Alexander Gordeev
2024-04-15 14:22   ` David Hildenbrand
2024-04-15 14:27   ` Christian Borntraeger [this message]
2024-04-15 14:52 ` Alexander Gordeev
2024-04-15 18:43 ` Muhammad Usama Anjum

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=743bd638-2a9d-4c53-bc44-14292edef58a@linux.ibm.com \
    --to=borntraeger@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=shuah@kernel.org \
    --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