From: Vivek Goyal <vgoyal@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: How does kdump deal with trampoline allocation?
Date: Tue, 28 Dec 2010 05:36:51 +0530 [thread overview]
Message-ID: <20101228000651.GB4142@redhat.com> (raw)
In-Reply-To: <4D18F798.4010708@zytor.com>
On Mon, Dec 27, 2010 at 12:31:20PM -0800, H. Peter Anvin wrote:
> Hi guys,
>
> I'm planning a major overhaul of the trampoline allocation in x86, and
> I'm trying to understand how kdump deals with it. The trampoline has to
> be allocated in low memory (< 1 MiB) and obviously that doesn't include
> the kdump area at all.
Hi Peter,
Kdump has the concept of backup area. We backup the contents of first
640KB of physical RAM in kdump reserved area and then allow kdump kernel
to use first 640KB of memory. So any trampoline allocation can be done
in low memory area without overwritting the contents of first kernel.
Thanks
Vivek
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2010-12-28 0:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 20:31 How does kdump deal with trampoline allocation? H. Peter Anvin
2010-12-28 0:06 ` Vivek Goyal [this message]
2010-12-28 0:13 ` H. Peter Anvin
2010-12-28 7:40 ` Eric W. Biederman
2010-12-28 20:11 ` H. Peter Anvin
2010-12-29 4:13 ` Eric W. Biederman
2010-12-29 6:25 ` H. Peter Anvin
2010-12-29 8:37 ` Eric W. Biederman
2011-01-03 5:01 ` Vivek Goyal
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=20101228000651.GB4142@redhat.com \
--to=vgoyal@redhat.com \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.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