From: ebiederm@xmission.com (Eric W. Biederman)
To: "H. Peter Anvin" <hpa@zytor.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: Wed, 29 Dec 2010 00:37:04 -0800 [thread overview]
Message-ID: <m1tyhxt1ov.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <4D1AD463.9050202@zytor.com> (H. Peter Anvin's message of "Tue, 28 Dec 2010 22:25:39 -0800")
"H. Peter Anvin" <hpa@zytor.com> writes:
> On 12/28/2010 08:13 PM, Eric W. Biederman wrote:
>> "H. Peter Anvin" <hpa@zytor.com> writes:
>>>
>>> Well, the trampoline is optional only on 32 bits, and with my changes,
>>> it would be unconditional.
>>
>> What motivates your trampoline rewrite?
>>
>
> The fact that so far four different pieces of code have low memory
> trampolines, and each is implemented differently. Furthermore, I'm
> currently being forced to work on a fifth. This unifies all that code,
> but it also makes it unconditional since at least reboot=bios is always
> going to need to be there.
That makes some sense. I remember seeing your complaining about how
many different flavors of physical page tables we have.
When your patches are ready cc me and I will be happy to look them
over and see if I can spot anything you might have missed.
Eric
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2010-12-29 8:37 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
2010-12-29 4:13 ` Eric W. Biederman
2010-12-29 6:25 ` H. Peter Anvin
2010-12-29 8:37 ` Eric W. Biederman [this message]
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=m1tyhxt1ov.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=hpa@zytor.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.