From: "H. Peter Anvin" <hpa@zytor.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: X86-ML <x86@kernel.org>, KEXEC-ML <kexec@lists.infradead.org>,
"Ahmed S. Darwish" <darwish.07@gmail.com>,
Haren Myneni <hbabu@us.ibm.com>,
Simon Horman <horms@verge.net.au>, Ingo Molnar <mingo@elte.hu>,
Vivek Goyal <vgoyal@redhat.com>
Subject: Re: Saveoops: Making Kexec purgatory position-independent?
Date: Sun, 27 Feb 2011 17:39:24 -0800 [thread overview]
Message-ID: <4D6AFCCC.7050705@zytor.com> (raw)
In-Reply-To: <m14o7q5m6d.fsf@fess.ebiederm.org>
On 02/26/2011 04:57 PM, Eric W. Biederman wrote:
>
> This isn't a case of the code not being position independent. This is
> case of where the relocations are applied.
>
This is a generic comment and may not apply to this particular case, but
it's pretty easy on x86 to build a chunk of code which is
self-relocating, meaning that it can be jumped to at any address without
any pre-relocation and do the necessary relocations itself.
-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
prev parent reply other threads:[~2011-02-28 1:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-26 16:20 Saveoops: Making Kexec purgatory position-independent? Ahmed S. Darwish
2011-02-26 21:38 ` H. Peter Anvin
2011-02-27 0:57 ` Eric W. Biederman
2011-02-27 1:15 ` H. Peter Anvin
2011-02-27 13:24 ` Ahmed S. Darwish
2011-02-27 14:16 ` Vivek Goyal
2011-02-27 15:43 ` Ahmed S. Darwish
2011-02-27 18:32 ` Eric W. Biederman
2011-02-28 1:38 ` Simon Horman
2011-02-28 1:39 ` H. Peter Anvin [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=4D6AFCCC.7050705@zytor.com \
--to=hpa@zytor.com \
--cc=darwish.07@gmail.com \
--cc=ebiederm@xmission.com \
--cc=hbabu@us.ibm.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=mingo@elte.hu \
--cc=vgoyal@redhat.com \
--cc=x86@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