All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>, Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: How does the handover from boot allocator to real allocator work
Date: Fri, 15 Sep 2006 14:08:01 -0700	[thread overview]
Message-ID: <450B1631.40307@goop.org> (raw)

Hi Ingo,

I'm digging around trying to work out how the handover from the 
boot-time allocator to the real memory management works. 

I'm missing something important though:  bootmem.c:free_all_bootmem() 
seems to end up just putting all low memory on the freelists.  How does 
this not put the kernel text+data pages on the freelists?  Also, 
presumably things allocated in the bootmem allocator remain allocated 
for the life of the running kernel?

I'm having a problem in my Xen kernel, in which free_init_pages() ends 
up getting a bad_page() warning because pfn 1024 has the PG_buddy bit 
set on it, which was unexpected (this page ends up being in the middle 
of the initdata section).  Page 1024 gets PF_buddy set by 
free_all_bootmem_core(), and it becomes an order 10 page.

I presume this is broken because free_all_bootmem_core() shouldn't be 
putting the kernel text+data into the freelists, but I don't see how 
this is prevented in the normal i386 case.  I'm guessing it's done by 
something like reserve_bootmem(), but I don't see such a call which 
would reserve the kernel itself.

What am I missing?

Thanks,
    J

                 reply	other threads:[~2006-09-15 21:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=450B1631.40307@goop.org \
    --to=jeremy@goop.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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.