From: Nina Schoetterl-Glausch <nsg@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, frankja@linux.ibm.com,
borntraeger@de.ibm.com, seiden@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 v1 4/5] KVM: s390: refactor and split some gmap helpers
Date: Wed, 21 May 2025 17:30:00 +0200 [thread overview]
Message-ID: <d495d17902955839b0d7d092334b47efbdcb55a1.camel@linux.ibm.com> (raw)
In-Reply-To: <20250521171930.2edaaa8a@p-imbrenda>
On Wed, 2025-05-21 at 17:19 +0200, Claudio Imbrenda wrote:
> On Wed, 21 May 2025 16:55:18 +0200
> Nina Schoetterl-Glausch <nsg@linux.ibm.com> wrote:
>
> > On Wed, 2025-05-14 at 18:38 +0200, 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>
> > > ---
> > > MAINTAINERS | 2 +
> > > arch/s390/include/asm/gmap_helpers.h | 18 ++
> > > arch/s390/kvm/diag.c | 11 +-
> > > arch/s390/kvm/kvm-s390.c | 3 +-
> > > arch/s390/mm/Makefile | 2 +
> > > arch/s390/mm/gmap.c | 46 ++---
> > > arch/s390/mm/gmap_helpers.c | 266 +++++++++++++++++++++++++++
> > > 7 files changed, 307 insertions(+), 41 deletions(-)
> > > create mode 100644 arch/s390/include/asm/gmap_helpers.h
> > > create mode 100644 arch/s390/mm/gmap_helpers.c
> > >
[...]
> > > +void __gmap_helper_zap_one(struct mm_struct *mm, unsigned long vmaddr)
> >
> > __gmap_helper_zap_mapping_pte ?
>
> but I'm not taking a pte as parameter
The pte being zapped is the one mapping vmaddr, right?
>
> >
> > > +{
> > > + struct vm_area_struct *vma;
> > > + spinlock_t *ptl;
> > > + pte_t *ptep;
> > > +
> > > + mmap_assert_locked(mm);
> > > +
> > > + /* Find the vm address for the guest address */
> > > + vma = vma_lookup(mm, vmaddr);
> > > + if (!vma || is_vm_hugetlb_page(vma))
> > > + return;
> > > +
> > > + /* Get pointer to the page table entry */
> > > + ptep = get_locked_pte(mm, vmaddr, &ptl);
> > > + if (!likely(ptep))
> >
> > if (unlikely(!ptep)) reads nicer to me.
>
> ok
>
> >
> > > + return;
> > > + if (pte_swap(*ptep))
> > > + ptep_zap_swap_entry(mm, pte_to_swp_entry(*ptep));
> > > + pte_unmap_unlock(ptep, ptl);
> > > +}
> > > +EXPORT_SYMBOL_GPL(__gmap_helper_zap_one);
> >
> > Looks reasonable, but I'm not well versed enough in mm code to evaluate
> > that with confidence.
> >
> > > +
> > > +void __gmap_helper_discard(struct mm_struct *mm, unsigned long vmaddr, unsigned long end)
> >
> > Maybe call this gmap_helper_discard_nolock or something.
>
> maybe __gmap_helper_discard_unlocked?
>
> the __ prefix often implies lack of locking
_nolock *definitely* implies it :P
[...]
> >
> > The stuff below is from arch/s390/mm/gmap.c right?
> > Are you going to delete it from there?
>
> not in this series, but the next series will remove mm/gmap.c altogether
Can't you do it with this one?
[...]
--
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Wolfgang Wendt
Geschäftsführung: David Faller
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294
next prev parent reply other threads:[~2025-05-21 15:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 16:38 [PATCH v1 0/5] KVM: s390: some cleanup and small fixes Claudio Imbrenda
2025-05-14 16:38 ` [PATCH v1 1/5] s390: remove unneeded includes Claudio Imbrenda
2025-05-15 13:56 ` Christoph Schlameuss
2025-05-15 15:29 ` Claudio Imbrenda
2025-05-14 16:38 ` [PATCH v1 2/5] KVM: s390: remove unneeded srcu lock Claudio Imbrenda
2025-05-19 8:25 ` Christian Borntraeger
2025-05-19 14:42 ` Nina Schoetterl-Glausch
2025-05-20 14:34 ` Nina Schoetterl-Glausch
2025-06-27 8:45 ` Christian Borntraeger
2025-05-14 16:38 ` [PATCH v1 3/5] KVM: s390: refactor some functions in priv.c Claudio Imbrenda
2025-05-20 12:49 ` Nina Schoetterl-Glausch
2025-05-20 14:39 ` Claudio Imbrenda
2025-05-14 16:38 ` [PATCH v1 4/5] KVM: s390: refactor and split some gmap helpers Claudio Imbrenda
2025-05-21 14:55 ` Nina Schoetterl-Glausch
2025-05-21 15:19 ` Claudio Imbrenda
2025-05-21 15:30 ` Nina Schoetterl-Glausch [this message]
2025-05-21 15:41 ` Claudio Imbrenda
2025-05-21 15:46 ` Nina Schoetterl-Glausch
2025-05-14 16:38 ` [PATCH v1 5/5] KVM: s390: simplify and move pv code Claudio Imbrenda
2025-05-21 15:42 ` Nina Schoetterl-Glausch
2025-05-14 17:41 ` [PATCH v1 0/5] KVM: s390: some cleanup and small fixes David Hildenbrand
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=d495d17902955839b0d7d092334b47efbdcb55a1.camel@linux.ibm.com \
--to=nsg@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=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;
as well as URLs for NNTP newsgroup(s).