From: Itsuro Oda <oda@valinux.co.jp>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: fastboot@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [Fastboot] Yet another crash dump tool
Date: Fri, 07 Jan 2005 08:55:37 +0900 [thread overview]
Message-ID: <20050107083247.6C54.ODA@valinux.co.jp> (raw)
In-Reply-To: <m1y8f7nn75.fsf@ebiederm.dsl.xmission.com>
Hi,
On 05 Jan 2005 22:25:34 -0700
ebiederm@xmission.com (Eric W. Biederman) wrote:
> One of the problems Hariprasad and Vivek seem to have been having is
> that the keeping the crash dump kernel from using the first 1M. You
> have avoided that problem correct?
alloc_pages(ZONE_NORMAL) is used to get memory area for the mini kernel
in "4MB unit"(i386). So the pages is never under 1M.
(for x86_64, alloc_bootmem is used to reserve the memory for the mini
kernel. alloc_pages does not guarantee under 4GB!!)
> As I recall from looking at your patch and it was obviously your last
> version was that you were using kmalloc or get_free_pages for some
> of your data structures that controlled the loaded of the mini kernel
> instead of allocating those data structures from the reserved area.
yes. kmalloc is used to get kimage struct. Indeed it is more safe to
put such structues in the reserved area (and write protected).
Thank you for your indication.
> Eric
Thanks.
--
Itsuro ODA <oda@valinux.co.jp>
prev parent reply other threads:[~2005-01-07 0:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 23:05 Itsuro Oda
2004-10-14 11:29 ` Robin Holt
2004-10-15 0:08 ` Itsuro Oda
2004-10-15 13:06 ` Robin Holt
2004-10-18 3:33 ` Itsuro Oda
2004-12-23 11:59 ` [Fastboot] " Eric W. Biederman
2005-01-06 1:54 ` Itsuro Oda
2005-01-06 5:25 ` Eric W. Biederman
2005-01-06 23:55 ` Itsuro Oda [this message]
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=20050107083247.6C54.ODA@valinux.co.jp \
--to=oda@valinux.co.jp \
--cc=ebiederm@xmission.com \
--cc=fastboot@osdl.org \
--cc=linux-kernel@vger.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®