From: Jeff Dike <jdike@addtoit.com>
To: Jason Lunz <lunz@falooley.org>
Cc: Blaisorblade <blaisorblade@yahoo.it>,
user-mode-linux-devel@lists.sourceforge.net,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [uml-devel] [UML] fix crash in block layer
Date: Fri, 16 Feb 2007 13:40:48 -0500 [thread overview]
Message-ID: <20070216184048.GA7481@ccure.user-mode-linux.org> (raw)
In-Reply-To: <20070216170207.GC2427@metaxa.reflex>
On Fri, Feb 16, 2007 at 12:02:08PM -0500, Jason Lunz wrote:
> I agree - I have only a vague idea about what uml_reserved means.
This is ancient code - after a quick look through it, I think what is
happening is this:
Early in boot, there are both libc and kernel (bootmem) memory
allocations happening. We can't redirect malloc to kmalloc yet, so
mallocs are allowed to happen until kmalloc is running. This requires
that the memory setup code leave some empty room in the address space
for malloc to grow into. The end of this area is uml_reserved.
When we are ready to turn on kmalloc, the rest of UML physical
memory (beyond uml_reserved) was already available to the bootmem
allocator, and it is just released to the page allocator. The area
that wasn't malloced by libc is released separately to the page
allocator.
At that point, uml_reserved loses its meaning, since memory on
either side of it is treated identically by the page allocator.
> Jeff, please drop my other patch and use this one.
OK.
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2007-02-16 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070215160001.GA6774@avocado.homenet>
2007-02-15 17:09 ` [uml-devel] [UML] fix crash in block layer Jeff Dike
2007-02-15 19:29 ` Blaisorblade
2007-02-16 17:02 ` Jason Lunz
2007-02-16 18:40 ` Jeff Dike [this message]
2007-02-19 22:28 ` Blaisorblade
2007-02-16 19:10 ` Blaisorblade
2007-02-09 22:01 Jason Lunz
-- strict thread matches above, loose matches on Subject: below --
2007-02-09 21:30 Jason Lunz
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=20070216184048.GA7481@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade@yahoo.it \
--cc=jens.axboe@oracle.com \
--cc=lunz@falooley.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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.