From: Thomas Gleixner <tglx@linutronix.de>
To: Feng Tang <feng.tang@intel.com>
Cc: Michal Hocko <mhocko@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, x86@kernel.org,
Ingo Molnar <mingo@elte.hu>,
"H . Peter Anvin" <hpa@linux.intel.com>,
Yinghai Lu <yinghai@kernel.org>,
Dave Hansen <dave.hansen@intel.com>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] x86, mm: Reserver some memory for bootmem allocator for NO_BOOTMEM
Date: Fri, 7 Sep 2018 12:52:17 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1809071250240.1402@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20180907081716.bxw3hmcl6w7gqvax@shbuild888>
On Fri, 7 Sep 2018, Feng Tang wrote:
> On Fri, Aug 31, 2018 at 09:36:59PM +0800, Feng Tang wrote:
> > Any sugestion? I can only have patch like this:
>
> Could you review this patch, as at this time window there is no usable memory
> block or other memory allocators that I know, so I follow the exisitng static
> fixmap page table code and add one more.
You really want to add a proper sanity check for this. The static stuff has
to cover the fixmap. Just making it work for this particular case is sloppy
at best as the next larger change of the fixmap will just bring the problem
back.
Thanks,
tglx
next prev parent reply other threads:[~2018-09-07 10:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 9:03 Feng Tang
2018-08-30 10:44 ` Peter Zijlstra
2018-08-30 11:12 ` Michal Hocko
2018-08-30 11:54 ` Thomas Gleixner
2018-08-30 12:49 ` Michal Hocko
2018-08-30 12:59 ` Feng Tang
2018-08-30 13:05 ` Thomas Gleixner
2018-08-30 13:19 ` Feng Tang
2018-08-30 13:25 ` Thomas Gleixner
2018-08-30 13:55 ` Feng Tang
2018-08-31 6:15 ` Feng Tang
2018-08-31 11:33 ` Thomas Gleixner
2018-08-31 13:36 ` Feng Tang
2018-09-07 8:17 ` Feng Tang
2018-09-07 10:52 ` Thomas Gleixner [this message]
2018-09-10 9:39 ` Feng Tang
2018-09-10 9:53 ` Thomas Gleixner
2018-09-11 6:14 ` Feng Tang
2018-09-15 10:29 ` Thomas Gleixner
2018-09-15 16:47 ` Feng Tang
2018-09-15 17:28 ` Thomas Gleixner
2018-09-16 14:35 ` Feng Tang
2018-09-16 14:43 ` Thomas Gleixner
2018-09-16 15:06 ` Feng Tang
2018-09-17 7:01 ` Feng Tang
2018-09-17 7:01 ` Thomas Gleixner
2018-08-30 12:09 ` Peter Zijlstra
2018-08-30 12:39 ` Michal Hocko
2018-08-30 12:43 ` Feng Tang
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=alpine.DEB.2.21.1809071250240.1402@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=ak@linux.intel.com \
--cc=dave.hansen@intel.com \
--cc=feng.tang@intel.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®