From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Nico Boehr <nrb@linux.ibm.com>
Cc: borntraeger@linux.ibm.com, frankja@linux.ibm.com,
shuah@kernel.org, kvm@vger.kernel.org,
linux-s390@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2 0/2] KVM: s390: CMMA migration selftest and small bugfix
Date: Wed, 17 May 2023 16:34:23 +0200 [thread overview]
Message-ID: <20230517163423.2e8a5bce@p-imbrenda> (raw)
In-Reply-To: <168379811019.9368.1588862499018469612@t14-nrb>
On Thu, 11 May 2023 11:41:50 +0200
Nico Boehr <nrb@linux.ibm.com> wrote:
> Quoting Nico Boehr (2023-03-24 15:54:22)
> > v2:
> > ---
> > * swap order of patches (thanks Claudio)
> > * add r-b
> > * add comment why memslots are zeroed
> >
> > Add a new selftest for CMMA migration. Also fix a small issue found during
> > development of the test.
> >
> > Nico Boehr (2):
> > KVM: s390: fix KVM_S390_GET_CMMA_BITS for GFNs in memslot holes
> > KVM: s390: selftests: add selftest for CMMA migration
> >
> > arch/s390/kvm/kvm-s390.c | 4 +
> > tools/testing/selftests/kvm/Makefile | 1 +
> > tools/testing/selftests/kvm/s390x/cmma_test.c | 680 ++++++++++++++++++
> > 3 files changed, 685 insertions(+)
> > create mode 100644 tools/testing/selftests/kvm/s390x/cmma_test.c
> >
> > --
> > 2.39.1
> >
>
> Polite ping.
Ooops, I thought this had already been picked
I'll queue it for 6.5
prev parent reply other threads:[~2023-05-17 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 14:54 [PATCH v2 0/2] KVM: s390: CMMA migration selftest and small bugfix Nico Boehr
2023-03-24 14:54 ` [PATCH v2 1/2] KVM: s390: fix KVM_S390_GET_CMMA_BITS for GFNs in memslot holes Nico Boehr
2023-05-12 7:20 ` Janosch Frank
2023-05-12 7:54 ` Nico Boehr
2023-03-24 14:54 ` [PATCH v2 2/2] KVM: s390: selftests: add selftest for CMMA migration Nico Boehr
2023-03-24 17:24 ` Claudio Imbrenda
2023-05-11 9:41 ` [PATCH v2 0/2] KVM: s390: CMMA migration selftest and small bugfix Nico Boehr
2023-05-17 14:34 ` Claudio Imbrenda [this message]
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=20230517163423.2e8a5bce@p-imbrenda \
--to=imbrenda@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=shuah@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