From: Miles Chen <miles.chen@mediatek.com>
To: David Hildenbrand <david@redhat.com>
Cc: wsd_upstream@mediatek.com, linux-kernel@vger.kernel.org,
Mike Rapoport <rppt@linux.ibm.com>,
linux-mm@kvack.org, linux-mediatek@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] mm/memblock: export max_pfn for kernel modules
Date: Thu, 4 Jun 2020 11:39:47 +0800 [thread overview]
Message-ID: <1591241987.29475.19.camel@mtkswgap22> (raw)
In-Reply-To: <23a9a2cc-3461-52bb-4285-b063a01bd7c6@redhat.com>
On Wed, 2020-06-03 at 18:16 +0200, David Hildenbrand wrote:
> On 03.06.20 18:11, Miles Chen wrote:
> > max_pfn is uesd to get the highest pfn in the system. Drivers like
> > drivers/iommu/mtk_iommu.c checks max_pfn to see if it should enable
> > its "4GB mode".
> >
> > This patch exports the max_pfn symbol, so we can build the driver as
> > a kernel module.
>
> Please add that change to the respective user patch (and cc MM-people
> for that patch), so we have the actual user right along the change and
> can figure out if this is the right thing to do.
>
Thanks for the comment.
Mike points out another alternative way to do this by totalram_pages().
I will use that approach so we don't have to export max_pfn here.
https://lkml.org/lkml/2020/6/3/771
Miles
> >
> > Signed-off-by: Miles Chen <miles.chen@mediatek.com>
> > ---
> > mm/memblock.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/mm/memblock.c b/mm/memblock.c
> > index c79ba6f9920c..3b2b21ecebb6 100644
> > --- a/mm/memblock.c
> > +++ b/mm/memblock.c
> > @@ -99,6 +99,7 @@ EXPORT_SYMBOL(contig_page_data);
> > unsigned long max_low_pfn;
> > unsigned long min_low_pfn;
> > unsigned long max_pfn;
> > +EXPORT_SYMBOL(max_pfn);
> > unsigned long long max_possible_pfn;
> >
> > static struct memblock_region memblock_memory_init_regions[INIT_MEMBLOCK_REGIONS] __initdata_memblock;
> >
>
>
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Miles Chen <miles.chen@mediatek.com>
To: David Hildenbrand <david@redhat.com>
Cc: wsd_upstream@mediatek.com, linux-kernel@vger.kernel.org,
Mike Rapoport <rppt@linux.ibm.com>,
linux-mm@kvack.org, linux-mediatek@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] mm/memblock: export max_pfn for kernel modules
Date: Thu, 4 Jun 2020 11:39:47 +0800 [thread overview]
Message-ID: <1591241987.29475.19.camel@mtkswgap22> (raw)
In-Reply-To: <23a9a2cc-3461-52bb-4285-b063a01bd7c6@redhat.com>
On Wed, 2020-06-03 at 18:16 +0200, David Hildenbrand wrote:
> On 03.06.20 18:11, Miles Chen wrote:
> > max_pfn is uesd to get the highest pfn in the system. Drivers like
> > drivers/iommu/mtk_iommu.c checks max_pfn to see if it should enable
> > its "4GB mode".
> >
> > This patch exports the max_pfn symbol, so we can build the driver as
> > a kernel module.
>
> Please add that change to the respective user patch (and cc MM-people
> for that patch), so we have the actual user right along the change and
> can figure out if this is the right thing to do.
>
Thanks for the comment.
Mike points out another alternative way to do this by totalram_pages().
I will use that approach so we don't have to export max_pfn here.
https://lkml.org/lkml/2020/6/3/771
Miles
> >
> > Signed-off-by: Miles Chen <miles.chen@mediatek.com>
> > ---
> > mm/memblock.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/mm/memblock.c b/mm/memblock.c
> > index c79ba6f9920c..3b2b21ecebb6 100644
> > --- a/mm/memblock.c
> > +++ b/mm/memblock.c
> > @@ -99,6 +99,7 @@ EXPORT_SYMBOL(contig_page_data);
> > unsigned long max_low_pfn;
> > unsigned long min_low_pfn;
> > unsigned long max_pfn;
> > +EXPORT_SYMBOL(max_pfn);
> > unsigned long long max_possible_pfn;
> >
> > static struct memblock_region memblock_memory_init_regions[INIT_MEMBLOCK_REGIONS] __initdata_memblock;
> >
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Miles Chen <miles.chen@mediatek.com>
To: David Hildenbrand <david@redhat.com>
Cc: Mike Rapoport <rppt@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Matthias Brugger <matthias.bgg@gmail.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>, <wsd_upstream@mediatek.com>
Subject: Re: [PATCH] mm/memblock: export max_pfn for kernel modules
Date: Thu, 4 Jun 2020 11:39:47 +0800 [thread overview]
Message-ID: <1591241987.29475.19.camel@mtkswgap22> (raw)
In-Reply-To: <23a9a2cc-3461-52bb-4285-b063a01bd7c6@redhat.com>
On Wed, 2020-06-03 at 18:16 +0200, David Hildenbrand wrote:
> On 03.06.20 18:11, Miles Chen wrote:
> > max_pfn is uesd to get the highest pfn in the system. Drivers like
> > drivers/iommu/mtk_iommu.c checks max_pfn to see if it should enable
> > its "4GB mode".
> >
> > This patch exports the max_pfn symbol, so we can build the driver as
> > a kernel module.
>
> Please add that change to the respective user patch (and cc MM-people
> for that patch), so we have the actual user right along the change and
> can figure out if this is the right thing to do.
>
Thanks for the comment.
Mike points out another alternative way to do this by totalram_pages().
I will use that approach so we don't have to export max_pfn here.
https://lkml.org/lkml/2020/6/3/771
Miles
> >
> > Signed-off-by: Miles Chen <miles.chen@mediatek.com>
> > ---
> > mm/memblock.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/mm/memblock.c b/mm/memblock.c
> > index c79ba6f9920c..3b2b21ecebb6 100644
> > --- a/mm/memblock.c
> > +++ b/mm/memblock.c
> > @@ -99,6 +99,7 @@ EXPORT_SYMBOL(contig_page_data);
> > unsigned long max_low_pfn;
> > unsigned long min_low_pfn;
> > unsigned long max_pfn;
> > +EXPORT_SYMBOL(max_pfn);
> > unsigned long long max_possible_pfn;
> >
> > static struct memblock_region memblock_memory_init_regions[INIT_MEMBLOCK_REGIONS] __initdata_memblock;
> >
>
>
next prev parent reply other threads:[~2020-06-04 3:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 16:11 [PATCH] mm/memblock: export max_pfn for kernel modules Miles Chen
2020-06-03 16:11 ` Miles Chen
2020-06-03 16:11 ` Miles Chen
2020-06-03 16:16 ` David Hildenbrand
2020-06-03 16:16 ` David Hildenbrand
2020-06-03 16:16 ` David Hildenbrand
2020-06-04 3:39 ` Miles Chen [this message]
2020-06-04 3:39 ` Miles Chen
2020-06-04 3:39 ` Miles Chen
2020-06-03 17:06 ` Mike Rapoport
2020-06-03 17:06 ` Mike Rapoport
2020-06-03 17:06 ` Mike Rapoport
2020-06-04 3:39 ` Miles Chen
2020-06-04 3:39 ` Miles Chen
2020-06-04 3:39 ` Miles Chen
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=1591241987.29475.19.camel@mtkswgap22 \
--to=miles.chen@mediatek.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=matthias.bgg@gmail.com \
--cc=rppt@linux.ibm.com \
--cc=wsd_upstream@mediatek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.