linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: David Hildenbrand <david@redhat.com>
Cc: Wei Yang <richard.weiyang@gmail.com>,
	richard@nod.at, anton.ivanov@cambridgegreys.com,
	johannes@sipsolutions.net, linux-um@lists.infradead.org,
	linux-mm@kvack.org, Jason Lunz <lunz@falooley.org>,
	Jeff Dike <jdike@linux.intel.com>,
	Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>,
	Alasdair G Kergon <agk@redhat.com>,
	Jens Axboe <jens.axboe@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Tiezhu Yang <yangtiezhu@loongson.cn>
Subject: Re: [PATCH] um/mm: get max_low_pfn from memblock
Date: Fri, 14 Jun 2024 10:51:32 +0300	[thread overview]
Message-ID: <Zmv2hHamxBh0_Gew@kernel.org> (raw)
In-Reply-To: <d21c00f1-bd9d-48ae-bb54-86cf126c45ef@redhat.com>

On Fri, Jun 14, 2024 at 09:31:59AM +0200, David Hildenbrand wrote:
> On 14.06.24 03:58, Wei Yang wrote:
> > Current calculation of max_low_pfn is introduced in commit af84eab20891
> > ("[PATCH] uml: fix LVM crash"). It is intended to set max_low_pfn to the
> > same value as max_pfn.
> > 
> > But I am not sure why the max_pfn is set to totalram_pages, which
> > represents the number of usable pages in system instead of an absolute
> > page frame number. (The change history stops there.)
> > 
> > While we can get the maximum page frame number from memblock, this looks
> > more reasonable than setting to totalram_pages.
> > 
> > Also this would help changing totalram_pages accounting, since we plan
> > to move the accounting into __free_pages_core(). With this change,
> > totalram_pages may not represent the total usable pages at this point,
> > since some pages would be deferred initialized.
> 
> Question is if deferred page init is even a thing on UM. But it certainly looks odd+suspiciously wrong to rely on totalram_pages().
 
As long as there is no HIGHMEM, 

max_pfn = max_low_pfn = PFN_DOWN(memblock_end_of_DRAM())

should be ok.
 
> > Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
> > CC: Jason Lunz <lunz@falooley.org>
> > CC: Jeff Dike <jdike@linux.intel.com>
> > Cc: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
> > Cc: Alasdair G Kergon <agk@redhat.com>
> > Cc: Jens Axboe <jens.axboe@oracle.com>
> > CC: Andrew Morton <akpm@linux-foundation.org>
> > CC: Mike Rapoport (IBM) <rppt@kernel.org>
> > CC: David Hildenbrand <david@redhat.com>
> > 
> > ---
> > A simple UML bootup test looks good.
> > ---
> >   arch/um/kernel/mem.c | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/arch/um/kernel/mem.c b/arch/um/kernel/mem.c
> > index ca91accd64fc..ca682879e28f 100644
> > --- a/arch/um/kernel/mem.c
> > +++ b/arch/um/kernel/mem.c
> > @@ -73,7 +73,7 @@ void __init mem_init(void)
> >   	/* this will put all low memory onto the freelists */
> >   	memblock_free_all();
> > -	max_low_pfn = totalram_pages();
> > +	max_low_pfn = PFN_DOWN(memblock_end_of_DRAM());

This assignment seem redundant as there is already

	max_low_pfn = min_low_pfn + (map_size >> PAGE_SHIFT);

in setup_physmem

> >   	max_pfn = max_low_pfn;
> >   	kmalloc_ok = 1;
> >   }
> 
> Matches what a bunch of other archs do.
> 
> Acked-by: David Hildenbrand <david@redhat.com>
> 
> 
> Randomly staring at other users:
> 
> arch/loongarch/kernel/numa.c:   max_low_pfn = PHYS_PFN(memblock_end_of_DRAM());
> arch/loongarch/kernel/setup.c:  max_low_pfn = PFN_PHYS(memblock_end_of_DRAM());
> 
> What? the latter cannot possibly be right, no? Looks odd at least.
> Only applies to CONFIG_OF_EARLY_FLATTREE. CCing loongarch maintainer.
> 
> -- 
> Cheers,
> 
> David / dhildenb
> 

-- 
Sincerely yours,
Mike.


  reply	other threads:[~2024-06-14  8:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-14  1:58 Wei Yang
2024-06-14  7:31 ` David Hildenbrand
2024-06-14  7:51   ` Mike Rapoport [this message]
2024-06-15  3:33     ` Wei Yang

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=Zmv2hHamxBh0_Gew@kernel.org \
    --to=rppt@kernel.org \
    --cc=agk@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=blaisorblade@yahoo.it \
    --cc=david@redhat.com \
    --cc=jdike@linux.intel.com \
    --cc=jens.axboe@oracle.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-mm@kvack.org \
    --cc=linux-um@lists.infradead.org \
    --cc=lunz@falooley.org \
    --cc=richard.weiyang@gmail.com \
    --cc=richard@nod.at \
    --cc=yangtiezhu@loongson.cn \
    /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