From: Janosch Frank <frankja@linux.ibm.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>, linux-kernel@vger.kernel.org
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
borntraeger@de.ibm.com, seiden@linux.ibm.com, nsg@linux.ibm.com,
nrb@linux.ibm.com, david@redhat.com, hca@linux.ibm.com,
agordeev@linux.ibm.com, svens@linux.ibm.com, gor@linux.ibm.com,
schlameuss@linux.ibm.com
Subject: Re: [PATCH v5 3/4] KVM: s390: Refactor and split some gmap helpers
Date: Wed, 28 May 2025 13:41:31 +0200 [thread overview]
Message-ID: <3ad77cfa-ab86-4bd0-92f8-04ef484dc3ac@linux.ibm.com> (raw)
In-Reply-To: <20250528095502.226213-4-imbrenda@linux.ibm.com>
On 5/28/25 11:55 AM, Claudio Imbrenda wrote:
> Refactor some gmap functions; move the implementation into a separate
> file with only helper functions. The new helper functions work on vm
> addresses, leaving all gmap logic in the gmap functions, which mostly
> become just wrappers.
>
> The whole gmap handling is going to be moved inside KVM soon, but the
> helper functions need to touch core mm functions, and thus need to
> stay in the core of kernel.
>
> Signed-off-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> Reviewed-by: Steffen Eiden <seiden@linux.ibm.com>
> Reviewed-by: Christoph Schlameuss <schlameuss@linux.ibm.com>
> ---
Acked-by: Janosch Frank <frankja@linux.ibm.com>
> MAINTAINERS | 2 +
> arch/s390/include/asm/gmap.h | 2 -
> arch/s390/include/asm/gmap_helpers.h | 15 ++
> arch/s390/kvm/diag.c | 30 +++-
> arch/s390/kvm/kvm-s390.c | 5 +-
> arch/s390/mm/Makefile | 2 +
> arch/s390/mm/gmap.c | 184 +---------------------
> arch/s390/mm/gmap_helpers.c | 221 +++++++++++++++++++++++++++
> 8 files changed, 274 insertions(+), 187 deletions(-)
> create mode 100644 arch/s390/include/asm/gmap_helpers.h
> create mode 100644 arch/s390/mm/gmap_helpers.c
>
[...]
> +#endif /* _ASM_S390_GMAP_HELPERS_H */
> diff --git a/arch/s390/kvm/diag.c b/arch/s390/kvm/diag.c
> index 74f73141f9b9..53233dec8cad 100644
> --- a/arch/s390/kvm/diag.c
> +++ b/arch/s390/kvm/diag.c
> @@ -11,12 +11,30 @@
> #include <linux/kvm.h>
> #include <linux/kvm_host.h>
> #include <asm/gmap.h>
> +#include <asm/gmap_helpers.h>
> #include <asm/virtio-ccw.h>
> #include "kvm-s390.h"
> #include "trace.h"
> #include "trace-s390.h"
> #include "gaccess.h"
>
> +static void do_discard_gfn_range(struct kvm_vcpu *vcpu, gfn_t gfn_start, gfn_t gfn_end)
> +{
A helper function for your helper function :)
next prev parent reply other threads:[~2025-05-28 11:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 9:54 [PATCH v5 0/4] KVM: s390: Some cleanup and small fixes Claudio Imbrenda
2025-05-28 9:54 ` [PATCH v5 1/4] s390: Remove unneeded includes Claudio Imbrenda
2025-05-28 9:55 ` [PATCH v5 2/4] KVM: s390: Remove unneeded srcu lock Claudio Imbrenda
2025-05-28 9:55 ` [PATCH v5 3/4] KVM: s390: Refactor and split some gmap helpers Claudio Imbrenda
2025-05-28 11:41 ` Janosch Frank [this message]
2025-05-28 9:55 ` [PATCH v5 4/4] KVM: s390: Simplify and move pv code Claudio Imbrenda
2025-05-28 12:15 ` Janosch Frank
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=3ad77cfa-ab86-4bd0-92f8-04ef484dc3ac@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=nsg@linux.ibm.com \
--cc=schlameuss@linux.ibm.com \
--cc=seiden@linux.ibm.com \
--cc=svens@linux.ibm.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