All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Borislav Petkov <bp@alien8.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Tejun Heo <tj@kernel.org>, Yinghai Lu <yinghai@kernel.org>,
	Mike Rapoport <rppt@linux.vnet.ibm.com>,
	Tang Chen <tangchen@cn.fujitsu.com>,
	Alexander Kuleshov <kuleshovmail@gmail.com>
Subject: Re: [RFC GIT PULL] EFI fixes, memblock quirk
Date: Tue, 19 Feb 2019 16:16:39 +0100	[thread overview]
Message-ID: <20190219151639.GA77461@gmail.com> (raw)
In-Reply-To: <CAHk-=wi=ooh9chSKyLipU6+eFbdfc680PUn3uKEoxLAMDMyMgg@mail.gmail.com>


* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Sun, Feb 17, 2019 at 2:59 AM Ingo Molnar <mingo@kernel.org> wrote:
> >
> > I marked it RFC: please have a second look at the mm/memblock.c change,
> > which adds a INIT_MEMBLOCK_RESERVED_REGIONS detour that ARM64 takes for
> > these systems.
> 
> It's not pretty, but it looks minimal for now. Pulled.

Thanks!

> > Perhaps we should upgrade the build time sizing of all platforms to
> > INIT_MEMBLOCK_REGIONS+NR_CPUS+1 and thus centrally give an extra
> > allocation entry per CPU configured?
> >
> > Or is there some cleaner solution?
> 
> Is there some reason other platforms might want that kind of thing?

Not that I'm aware of.

> If not, then the current hack seems sufficient.

Ok!

Thanks,

	Ingo

  reply	other threads:[~2019-02-19 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-17 10:59 [RFC GIT PULL] EFI fixes, memblock quirk Ingo Molnar
2019-02-17 17:24 ` Linus Torvalds
2019-02-19 15:16   ` Ingo Molnar [this message]
2019-02-19 15:29     ` Ard Biesheuvel

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=20190219151639.GA77461@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=benh@kernel.crashing.org \
    --cc=bp@alien8.de \
    --cc=kuleshovmail@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rppt@linux.vnet.ibm.com \
    --cc=tangchen@cn.fujitsu.com \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=yinghai@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 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.