linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Mike Rapoport <rppt@linux.ibm.com>,
	Vladimir Isaev <Vladimir.Isaev@synopsys.com>
Cc: "linux-snps-arc@lists.infradead.org"
	<linux-snps-arc@lists.infradead.org>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARC: Use max_high_pfn as a HIGHMEM zone border
Date: Mon, 26 Apr 2021 16:31:28 +0000	[thread overview]
Message-ID: <835d0c3f-ccba-e8d7-df4a-6c0ce5296e31@synopsys.com> (raw)
In-Reply-To: <YIbnO3BhOeUSRU0E@linux.ibm.com>

On 4/26/21 9:15 AM, Mike Rapoport wrote:
> On Mon, Apr 26, 2021 at 11:55:00AM +0000, Vladimir Isaev wrote:
>> Hi Mike,
>>
>> On Mon, April 26, 2021 2:29 PM, Mike Rapoport wrote:
>>> On Mon, Apr 26, 2021 at 01:10:04PM +0300, Vladimir Isaev wrote:
>>>> -	max_zone_pfn[ZONE_HIGHMEM] = min_low_pfn;
>>>> +	max_zone_pfn[ZONE_HIGHMEM] = max_high_pfn;
>>> This is correct with PAE40, but it will break !PAE40 when "highmem" has lower
>>> addresses than lowmem.
>>>
>>> It rather should be something like:
>>>
>>>          if (IS_ENABLED(CONFIG_ARC_HAS_PAE40))
>>>                  max_zone_pfn[ZONE_HIGHMEM] = max_high_pfn;
>>>          else
>>>              	max_zone_pfn[ZONE_HIGHMEM] = min_low_pfn;
>>>
>> Not sure if I understand why we should have min_low_pfn here. In !PAE40
>> case max_high_pfn just will be smaller than min_low_pfn.
> Hmm, actually, you are right. This should be fine.

But still worth adding a comment. If this could trip the person who did 
the massive cross-arch rework then I don't know what mere mortals would 
run into ;-)

-Vineet

      reply	other threads:[~2021-04-26 16:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26 10:10 Vladimir Isaev
2021-04-26 11:29 ` Mike Rapoport
2021-04-26 11:55   ` Vladimir Isaev
2021-04-26 16:15     ` Mike Rapoport
2021-04-26 16:31       ` Vineet Gupta [this message]

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=835d0c3f-ccba-e8d7-df4a-6c0ce5296e31@synopsys.com \
    --to=vineet.gupta1@synopsys.com \
    --cc=Vladimir.Isaev@synopsys.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=rppt@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