public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: Mike Rapoport <rppt@kernel.org>,
	Guenter Roeck <linux@roeck-us.net>, Rich Felker <dalias@libc.org>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	"x86@kernel.org" <x86@kernel.org>,
	Michal Hocko <mhocko@kernel.org>,
	"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
	Max Filippov <jcmvbkbc@gmail.com>, Guo Ren <guoren@kernel.org>,
	Ley Foon Tan <ley.foon.tan@intel.com>,
	"sparclinux@vger.kernel.org" <sparclinux@vger.kernel.org>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>,
	Greg Ungerer <gerg@linux-m68k.org>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	"linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>,
	"linux-c6x-dev@linux-c6x.org" <linux-c6x-dev@linux-c6x.org>,
	Baoquan He <bhe@redhat.com>, Jonathan Corbet <corbet@lwn.net>,
	"linux-hexagon@vger.kernel.org" <linux-hexagon@vger.kernel.org>,
	Helge Deller <deller@gmx.de>,
	"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
	Russell King <linux@armlinux.org.uk>,
	"linux-csky@vger.kernel.org" <linux-csky@vger.kernel.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH v2 17/20] mm: free_area_init: allow defining max_zone_pfn in descending order
Date: Tue, 5 May 2020 18:07:46 +0000	[thread overview]
Message-ID: <88b9465b-6e6d-86ca-3776-ccb7a5b60b7f@synopsys.com> (raw)
In-Reply-To: <20200505091946.GG342687@linux.ibm.com>

On 5/5/20 2:19 AM, Mike Rapoport wrote:
> From the code I've got the impression that it is either one of them. I.e
> the physical memory is either at
>
> 0x8000_0000 - <end of DDR 0 bank>
> 0x0000_0000 - <end of DDR 1 bank>
>
> or
>
> 0x0_8000_0000 - <end of DDR 0 bank>
> 0x1_0000_0000 - <end of DDR 1 bank>
>
> Is this possible to have a system with three live ranges? Like
>
> 0x0_0000_0000 - <end of DDR 1 bank>
> 0x0_8000_0000 - <end of DDR 0 bank>
> 0x1_0000_0000 - <end of DDR 2 bank>

We don't have such a system, but it is indeed possible in theory. The question is
 - Can other arches have such a setup too
 - Is it not better to have the core retain the flexibility just in case

Thx,
-Vineet

  reply	other threads:[~2020-05-05 18:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200429121126.17989-1-rppt@kernel.org>
     [not found] ` <20200429121126.17989-18-rppt@kernel.org>
     [not found]   ` <20200503174138.GA114085@roeck-us.net>
     [not found]     ` <20200503184300.GA154219@roeck-us.net>
     [not found]       ` <20200504153901.GM14260@kernel.org>
2020-05-05  6:23         ` [PATCH v2 17/20] mm: free_area_init: allow defining max_zone_pfn in descending order Vineet Gupta
2020-05-05  9:19           ` Mike Rapoport
2020-05-05 18:07             ` Vineet Gupta [this message]
2020-05-05 20:15               ` Mike Rapoport
2020-05-07 20:59                 ` Mike Rapoport
2020-05-07 21:21                   ` Vineet Gupta

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=88b9465b-6e6d-86ca-3776-ccb7a5b60b7f@synopsys.com \
    --to=vineet.gupta1@synopsys.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=bhe@redhat.com \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=dalias@libc.org \
    --cc=deller@gmx.de \
    --cc=geert@linux-m68k.org \
    --cc=gerg@linux-m68k.org \
    --cc=guoren@kernel.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=jcmvbkbc@gmail.com \
    --cc=ley.foon.tan@intel.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-c6x-dev@linux-c6x.org \
    --cc=linux-csky@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linux@roeck-us.net \
    --cc=mhocko@kernel.org \
    --cc=rppt@kernel.org \
    --cc=rppt@linux.ibm.com \
    --cc=sparclinux@vger.kernel.org \
    --cc=x86@kernel.org \
    /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