From: Michal Hocko <mhocko@kernel.org>
To: Dave Young <dyoung@redhat.com>
Cc: linux-kernel@vger.kernel.org, pasha.tatashin@oracle.com,
linux-mm@kvack.org, akpm@linux-foundation.org
Subject: Re: [PATCH] mm: check pfn_valid first in zero_resv_unavail
Date: Fri, 1 Dec 2017 10:42:15 +0100 [thread overview]
Message-ID: <20171201094215.aenoqa5jepdc3jd5@dhcp22.suse.cz> (raw)
In-Reply-To: <20171201092951.GA2943@dhcp-128-65.nay.redhat.com>
On Fri 01-12-17 17:29:51, Dave Young wrote:
> On 12/01/17 at 10:19am, Michal Hocko wrote:
> > On Fri 01-12-17 16:56:57, Dave Young wrote:
> > > On 11/30/17 at 10:35am, Michal Hocko wrote:
> > [...]
> > > > Can we exclude that range from the memblock allocator instead? E.g. what
> > > > happens if somebody allocates from that range?
> > >
> > > It is a EFI BGRT image buffer provided by firmware, they are reserved
> > > always and can not be used to allocate memory.
> >
> > Hmm, I see but I was actually suggesting to remove this range from the
> > memblock allocator altogether (memblock_remove) as it shouldn't be there
> > in the first place.
>
> Oh, I'm not sure because it is introduced as a way for efi to reserve
> boot services areas to be persistent across kexec reboot. See
> drivers/firmware/efi/efi.c: efi_mem_reserve(), BGRT is only one user
> of it, there is esrt and maybe other users, I do not know if it is safe
> :(
Hmm, so it this range ever backed by a valid pfn?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2017-12-01 9:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 6:04 [PATCH] mm: check pfn_valid first in zero_resv_unavail Dave Young
2017-11-30 9:35 ` Michal Hocko
2017-12-01 8:56 ` Dave Young
2017-12-01 9:19 ` Michal Hocko
2017-12-01 9:29 ` Dave Young
2017-12-01 9:42 ` Michal Hocko [this message]
2017-12-01 9:49 ` Dave Young
2017-11-30 17:25 ` Pavel Tatashin
2017-12-01 8:57 ` Dave Young
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=20171201094215.aenoqa5jepdc3jd5@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dyoung@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@oracle.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;
as well as URLs for NNTP newsgroup(s).