From: Steffen Eiden <seiden@linux.ibm.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
linux-s390@vger.kernel.org, borntraeger@de.ibm.com,
frankja@linux.ibm.com, david@kernel.org, nrb@linux.ibm.com,
schlameuss@linux.ibm.com, gra@linux.ibm.com, pbonzini@redhat.com,
seanjc@google.com, yan.y.zhao@intel.com,
isaku.yamahata@intel.com
Subject: Re: [PATCH v3 0/5] KVM: s390: Implement KVM_PRE_FAULT_MEMORY
Date: Wed, 27 May 2026 17:05:54 +0200 [thread overview]
Message-ID: <20260527150554.361644-A-seiden@linux.ibm.com> (raw)
In-Reply-To: <20260527144358.186359-1-imbrenda@linux.ibm.com>
On Wed, May 27, 2026 at 04:43:53PM +0200, Claudio Imbrenda wrote:
> Implement KVM_PRE_FAULT_MEMORY on s390, and update documentation and
> selftests accordingly.
>
...
> Claudio Imbrenda (5):
> KVM: s390: Track page size in struct guest_fault
> KVM: s390: Implement KVM_PRE_FAULT_MEMORY
> KVM: s390: Update KVM_PRE_FAULT_MEMORY API documentation
> KVM: selftests: Fix pre_fault_memory_test to run on s390
> KVM: selftests: Enable pre_fault_memory_test for s390
LGTM.
For the whole series:
Reviewed-by: Steffen Eiden <seiden@linux.ibm.com>
prev parent reply other threads:[~2026-05-27 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 14:43 [PATCH v3 0/5] KVM: s390: Implement KVM_PRE_FAULT_MEMORY Claudio Imbrenda
2026-05-27 14:43 ` [PATCH v3 1/5] KVM: s390: Track page size in struct guest_fault Claudio Imbrenda
2026-05-27 14:43 ` [PATCH v3 2/5] KVM: s390: Implement KVM_PRE_FAULT_MEMORY Claudio Imbrenda
2026-05-27 14:43 ` [PATCH v3 3/5] KVM: s390: Update KVM_PRE_FAULT_MEMORY API documentation Claudio Imbrenda
2026-05-27 14:43 ` [PATCH v3 4/5] KVM: selftests: Fix pre_fault_memory_test to run on s390 Claudio Imbrenda
2026-05-27 14:43 ` [PATCH v3 5/5] KVM: selftests: Enable pre_fault_memory_test for s390 Claudio Imbrenda
2026-05-27 15:05 ` Steffen Eiden [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=20260527150554.361644-A-seiden@linux.ibm.com \
--to=seiden@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@kernel.org \
--cc=frankja@linux.ibm.com \
--cc=gra@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=isaku.yamahata@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=schlameuss@linux.ibm.com \
--cc=seanjc@google.com \
--cc=yan.y.zhao@intel.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