All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
	"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	Vivek Goyal <vgoyal@redhat.com>
Subject: Re: How does kdump deal with trampoline allocation?
Date: Tue, 28 Dec 2010 12:11:21 -0800	[thread overview]
Message-ID: <4D1A4469.2060000@zytor.com> (raw)
In-Reply-To: <m1lj3auyzr.fsf@fess.ebiederm.org>

On 12/27/2010 11:40 PM, Eric W. Biederman wrote:
>>
>> OK, that's straightforward.  That presumably means that the low 640K is
>> marked unused in the memory map that memblock sees during early startup.
>>  That fits very cleanly with the patches I'm doing.
> 
> Additionally we typically start with maxcpus=1 so we don't strictly
> need the trampoline to start other cpus.
> 

Well, the trampoline is optional only on 32 bits, and with my changes,
it would be unconditional.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2010-12-28 20:11 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
2010-12-28  0:13   ` H. Peter Anvin
2010-12-28  7:40     ` Eric W. Biederman
2010-12-28 20:11       ` H. Peter Anvin [this message]
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=4D1A4469.2060000@zytor.com \
    --to=hpa@zytor.com \
    --cc=ebiederm@xmission.com \
    --cc=kexec@lists.infradead.org \
    --cc=vgoyal@redhat.com \
    --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 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.