public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christoph Schlameuss" <schlameuss@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>,
	<frankja@linux.ibm.com>, <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>
Subject: Re: [PATCH v3 3/4] KVM: s390: refactor and split some gmap helpers
Date: Thu, 22 May 2025 20:04:20 +0200	[thread overview]
Message-ID: <DA2VZ43MN9WS.I6PHR04W4WKV@linux.ibm.com> (raw)
In-Reply-To: <20250522132259.167708-4-imbrenda@linux.ibm.com>

On Thu May 22, 2025 at 3:22 PM CEST, 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.
>

Reviewed-by: Christoph Schlameuss <schlameuss@linux.ibm.com>

> Signed-off-by: Claudio Imbrenda <imbrenda@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                 |  13 +-
>  arch/s390/kvm/kvm-s390.c             |   5 +-
>  arch/s390/mm/Makefile                |   2 +
>  arch/s390/mm/gmap.c                  | 157 +------------------
>  arch/s390/mm/gmap_helpers.c          | 223 +++++++++++++++++++++++++++
>  8 files changed, 259 insertions(+), 160 deletions(-)
>  create mode 100644 arch/s390/include/asm/gmap_helpers.h
>  create mode 100644 arch/s390/mm/gmap_helpers.c

[...]


  parent reply	other threads:[~2025-05-22 18:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-22 13:22 [PATCH v3 0/4] KVM: s390: some cleanup and small fixes Claudio Imbrenda
2025-05-22 13:22 ` [PATCH v3 1/4] s390: remove unneeded includes Claudio Imbrenda
2025-05-22 13:50   ` Steffen Eiden
2025-05-22 13:22 ` [PATCH v3 2/4] KVM: s390: remove unneeded srcu lock Claudio Imbrenda
2025-05-22 13:44   ` Christoph Schlameuss
2025-05-22 13:57   ` Steffen Eiden
2025-05-22 13:22 ` [PATCH v3 3/4] KVM: s390: refactor and split some gmap helpers Claudio Imbrenda
2025-05-22 14:49   ` Steffen Eiden
2025-05-22 18:04   ` Christoph Schlameuss [this message]
2025-05-23  1:03   ` kernel test robot
2025-05-23  3:48   ` kernel test robot
2025-05-22 13:22 ` [PATCH v3 4/4] KVM: s390: simplify and move pv code Claudio Imbrenda
2025-05-22 14:57   ` Steffen Eiden
2025-05-22 18:40   ` Christoph Schlameuss

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=DA2VZ43MN9WS.I6PHR04W4WKV@linux.ibm.com \
    --to=schlameuss@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.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=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