From: "Huang, Ying" <ying.huang@intel.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Vivek Goyal <vgoyal@redhat.com>, Pavel Machek <pavel@ucw.cz>,
nigel@nigel.suspend2.net, "Rafael J. Wysocki" <rjw@sisk.pl>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: [PATCH] kexec based hibernation: a prototype of kexec multi-stage load
Date: Thu, 15 May 2008 10:40:07 +0800 [thread overview]
Message-ID: <1210819207.23707.107.camel@caritas-dev.intel.com> (raw)
In-Reply-To: <m1lk2c4l4i.fsf@frodo.ebiederm.org>
On Wed, 2008-05-14 at 14:43 -0700, Eric W. Biederman wrote:
> "Huang, Ying" <ying.huang@intel.com> writes:
>
> >> So, IMHO, for first simple implementation, we don't have to pass around
> >> any data between kernels except entry point. (Please correct me if I am
> >> wrong). Lets get that implementation in first and then we can get rest
> >> of the pieces in place.
> >
> > Yes. Kernel entry/re-entry point is the only information need to be
> > communicated between kernels for just switching between them. So we can
> > focus on kexec jump patch firstly.
>
> Then as a preliminary design let's plan on this.
>
> - Pass the rentry point as the return address (using the C ABI).
> We may want to load the stack pointer etc so we can act as
> a direct entry point for new code.
OK, I will try to do this.
> - Look at passing a pointer to the mapping of pages that the kexec
> trampoline uses in arg1 of the C ABI. Largely the format is defacto
> fixed anyway because we need to pass the structure from C to
> assembly.
You mean pass image->head to purgatory of /sbin/kexec using arg1 of C
ABI?
> Using the standard C ABI makes things much it much easier to pick
> a calling convention, and to document it.
Yes.
Best Regards,
Huang Ying
next prev parent reply other threads:[~2008-05-15 2:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 6:40 [PATCH] kexec based hibernation: a prototype of kexec multi-stage load Huang, Ying
2008-05-13 5:34 ` Vivek Goyal
2008-05-14 1:57 ` Huang, Ying
2008-05-14 2:56 ` Vivek Goyal
2008-05-14 3:37 ` Huang, Ying
2008-05-14 21:43 ` Eric W. Biederman
2008-05-15 2:40 ` Huang, Ying [this message]
2008-05-15 4:57 ` Huang, Ying
2008-05-15 18:39 ` Eric W. Biederman
2008-05-16 1:41 ` Huang, Ying
2008-05-16 2:25 ` Eric W. Biederman
2008-05-16 2:56 ` Huang, Ying
2008-05-16 3:27 ` Vivek Goyal
2008-05-16 13:40 ` Vivek Goyal
2008-05-18 1:59 ` Eric W. Biederman
2008-05-16 3:33 ` Eric W. Biederman
2008-05-16 2:00 ` Vivek Goyal
2008-05-16 2:19 ` Huang, Ying
2008-05-16 2:55 ` Eric W. Biederman
2008-05-16 4:52 ` Huang, Ying
2008-05-16 13:36 ` Vivek Goyal
2008-05-16 11:58 ` Pavel Machek
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=1210819207.23707.107.camel@caritas-dev.intel.com \
--to=ying.huang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@nigel.suspend2.net \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=vgoyal@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox