linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Gordeev <agordeev@linux.ibm.com>
To: Kevin Brodsky <kevin.brodsky@arm.com>
Cc: Qi Zheng <zhengqi.arch@bytedance.com>,
	Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
	Heiko Carstens <hca@linux.ibm.com>,
	linux-mm@kvack.org, linux-s390@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] s390/mm: Add missing ctor/dtor on page table upgrade
Date: Fri, 24 Jan 2025 09:24:58 +0100	[thread overview]
Message-ID: <Z5NOWvrOln4T0RCH@li-008a6a4c-3549-11b2-a85c-c5cc2836eea2.ibm.com> (raw)
In-Reply-To: <f1ff18a2-1b5e-4e9a-869b-9785faabf24d@arm.com>

On Fri, Jan 24, 2025 at 08:58:07AM +0100, Kevin Brodsky wrote:

Kevin,
...
> Thank you for putting together this patch! I was completely unaware of
> this "upgrade" path on s390.
...
> > diff --git a/arch/s390/mm/pgalloc.c b/arch/s390/mm/pgalloc.c
> > index a4e761902093..d33f55b7ee98 100644
> > --- a/arch/s390/mm/pgalloc.c
> > +++ b/arch/s390/mm/pgalloc.c
> > @@ -88,12 +88,14 @@ int crst_table_upgrade(struct mm_struct *mm, unsigned long end)
> >  		if (unlikely(!p4d))
> >  			goto err_p4d;
> >  		crst_table_init(p4d, _REGION2_ENTRY_EMPTY);
> > +		pagetable_p4d_ctor(virt_to_ptdesc(p4d));
> 
> This block seems to be equivalent to p4d_alloc_one(), maybe it would be
> preferable to just call p4d_alloc_one() here to avoid further mismatches
> in the future (and reduce duplication)?

Yes, I wanted to do exactly that (together with p4d_free() you noticed),
but then the whole thing with open coded pagetable_pgd_ctor() below gets
inconsistent. I would prefer to keep it this way as of now.

> >  	}
> >  	if (end > _REGION1_SIZE) {
> >  		pgd = crst_table_alloc(mm);
> >  		if (unlikely(!pgd))
> >  			goto err_pgd;
> >  		crst_table_init(pgd, _REGION1_ENTRY_EMPTY);
> > +		pagetable_pgd_ctor(virt_to_ptdesc(pgd));
> 
> I was hoping this might be equivalent to pgd_alloc() but it does not
> include a call to crst_table_init(). Since adding it would be apparently
> undesirable (having read the other thread), it seems reasonable to add
> the explicit constructor call.

We were thinking about a follow-up cleanup that addresses it all, but this
patch is a targeted fix to catch up your and Qi Zheng series in the still
open merge window.

> >  	}
> >  
> >  	spin_lock_bh(&mm->page_table_lock);
> > @@ -130,6 +132,7 @@ int crst_table_upgrade(struct mm_struct *mm, unsigned long end)
> >  	return 0;
> >  
> >  err_pgd:
> > +	pagetable_dtor(virt_to_ptdesc(p4d));
> >  	crst_table_free(mm, p4d);
> 
> Similarly, this could be a call to p4d_free().
> 
> - Kevin
> 
> >  err_p4d:
> >  	return -ENOMEM;

Thanks for the review!


  reply	other threads:[~2025-01-24  8:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23 16:03 Alexander Gordeev
2025-01-23 16:51 ` Gerald Schaefer
2025-01-24  2:43 ` Qi Zheng
2025-01-24  7:58 ` Kevin Brodsky
2025-01-24  8:24   ` Alexander Gordeev [this message]
2025-01-24 12:30     ` Kevin Brodsky
2025-01-24  9:29   ` Heiko Carstens
2025-01-24  9:39     ` Heiko Carstens
2025-01-24 12:39     ` Kevin Brodsky

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=Z5NOWvrOln4T0RCH@li-008a6a4c-3549-11b2-a85c-c5cc2836eea2.ibm.com \
    --to=agordeev@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=gerald.schaefer@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=kevin.brodsky@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=zhengqi.arch@bytedance.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