From: ebiederm@xmission.com (Eric W. Biederman)
To: Ming Lei <mlei@Brocade.COM>
Cc: kexec@lists.infradead.org
Subject: Re: should kernel image destination address be picked up by kernel itself?
Date: Tue, 03 Feb 2009 11:52:09 -0800 [thread overview]
Message-ID: <m14ozb1eom.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <4C94DE2070B172459E4F1EE14BD2364E027534BA@HQ-EXCH-5.corp.brocade.com> (Ming Lei's message of "Tue\, 27 Jan 2009 14\:22\:18 -0800")
"Ming Lei" <mlei@Brocade.COM> writes:
> As I understand the code, current destination address is picked up by
> either the user(elf image) or kexec-tools. It is not automatic, can we
> let linux kernel choose the address instead? It is automatic and no way
> to wipe out something important.
I don't follow. The basic model of kexec is:
- kexec is fed a standalone executables (things that run without OS
support)
- All of the policy decisions are made in user space (such as where to
execute from)
- standalone executables are loaded into an address space where
physical address and virtual address are the same.
- Sophisticated page swapping happens in the kernel where
sys_kexec_load was called so that any valid address on the machine
is available to the standalone executable.
What problem do you see in that model?
Why is it a problem for you?
Eric
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2009-02-03 19:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 22:22 should kernel image destination address be picked up by kernel itself? Ming Lei
2009-02-03 19:52 ` Eric W. Biederman [this message]
2009-02-03 20:06 ` Ming Lei
2009-02-03 21:42 ` Eric W. Biederman
2009-02-10 1:08 ` Ming Lei
2009-02-10 5:27 ` Eric W. Biederman
2009-02-10 21:34 ` Ming Lei
2009-04-16 18:48 ` Ming Lei
2009-04-20 21:19 ` Eric W. Biederman
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=m14ozb1eom.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=mlei@Brocade.COM \
/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.