All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Huang, Ying" <ying.huang@intel.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: nigel@nigel.suspend2.net,
	Kexec Mailing List <kexec@lists.infradead.org>,
	linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Pavel Machek <pavel@ucw.cz>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] kexec based hibernation: a prototype of kexec multi-stage load
Date: Fri, 16 May 2008 10:19:34 +0800	[thread overview]
Message-ID: <1210904374.23707.178.camel@caritas-dev.intel.com> (raw)
In-Reply-To: <20080516020043.GC6926@redhat.com>

On Thu, 2008-05-15 at 22:00 -0400, Vivek Goyal wrote:
[...]
> IMHO, this kind of make more sense to me when keeping C function like
> semantics in mind.
> 
> Both the cases can be treated like calls to functions (calling BIOS function
> and jumping to kernel B). The basic difference between two cases is the
> re-entry point. In BIOS function case, we always re-enter the function at the
> start but in case of kernel B, except first entry, all other entries happen
> at a run time determined address, which needs to be communicated to kernel A.
> 
> I would think that second kernel B just should execute "ret" and new entry
> address of kernel B is passed to kernel A through %eax (return value of
> function).

The disadvantage of this solution is that kernel B must know it is
original kernel (A) or kexeced kernel (B). Different code should be used
by kernel A and kernel B. And after jump from A to B, jump from B to A,
when jump from A to B again, kernel A must use different code from the
first time.

Best Regards,
Huang Ying


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

WARNING: multiple messages have this Message-ID (diff)
From: "Huang, Ying" <ying.huang@intel.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.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: Fri, 16 May 2008 10:19:34 +0800	[thread overview]
Message-ID: <1210904374.23707.178.camel@caritas-dev.intel.com> (raw)
In-Reply-To: <20080516020043.GC6926@redhat.com>

On Thu, 2008-05-15 at 22:00 -0400, Vivek Goyal wrote:
[...]
> IMHO, this kind of make more sense to me when keeping C function like
> semantics in mind.
> 
> Both the cases can be treated like calls to functions (calling BIOS function
> and jumping to kernel B). The basic difference between two cases is the
> re-entry point. In BIOS function case, we always re-enter the function at the
> start but in case of kernel B, except first entry, all other entries happen
> at a run time determined address, which needs to be communicated to kernel A.
> 
> I would think that second kernel B just should execute "ret" and new entry
> address of kernel B is passed to kernel A through %eax (return value of
> function).

The disadvantage of this solution is that kernel B must know it is
original kernel (A) or kexeced kernel (B). Different code should be used
by kernel A and kernel B. And after jump from A to B, jump from B to A,
when jump from A to B again, kernel A must use different code from the
first time.

Best Regards,
Huang Ying


  reply	other threads:[~2008-05-16  2:13 UTC|newest]

Thread overview: 44+ 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-12  6:40 ` Huang, Ying
2008-05-13  5:34 ` Vivek Goyal
2008-05-13  5:34   ` Vivek Goyal
2008-05-14  1:57   ` Huang, Ying
2008-05-14  1:57     ` Huang, Ying
2008-05-14  2:56     ` Vivek Goyal
2008-05-14  2:56       ` Vivek Goyal
2008-05-14  3:37       ` Huang, Ying
2008-05-14  3:37         ` Huang, Ying
2008-05-14 21:43         ` Eric W. Biederman
2008-05-14 21:43           ` Eric W. Biederman
2008-05-15  2:40           ` Huang, Ying
2008-05-15  2:40             ` Huang, Ying
2008-05-15  4:57           ` Huang, Ying
2008-05-15  4:57             ` Huang, Ying
2008-05-15 18:39             ` Eric W. Biederman
2008-05-15 18:39               ` Eric W. Biederman
2008-05-16  1:41               ` Huang, Ying
2008-05-16  1:41                 ` Huang, Ying
2008-05-16  2:25                 ` Eric W. Biederman
2008-05-16  2:25                   ` Eric W. Biederman
2008-05-16  2:56                   ` Huang, Ying
2008-05-16  2:56                     ` Huang, Ying
2008-05-16  3:27                     ` Vivek Goyal
2008-05-16  3:27                       ` Vivek Goyal
2008-05-16 13:40                       ` Vivek Goyal
2008-05-16 13:40                         ` Vivek Goyal
2008-05-18  1:59                       ` Eric W. Biederman
2008-05-18  1:59                         ` Eric W. Biederman
2008-05-16  3:33                     ` Eric W. Biederman
2008-05-16  3:33                       ` Eric W. Biederman
2008-05-16  2:00             ` Vivek Goyal
2008-05-16  2:00               ` Vivek Goyal
2008-05-16  2:19               ` Huang, Ying [this message]
2008-05-16  2:19                 ` Huang, Ying
2008-05-16  2:55                 ` Eric W. Biederman
2008-05-16  2:55                   ` Eric W. Biederman
2008-05-16  4:52                   ` Huang, Ying
2008-05-16  4:52                     ` Huang, Ying
2008-05-16 13:36                     ` Vivek Goyal
2008-05-16 13:36                       ` Vivek Goyal
2008-05-16 11:58   ` Pavel Machek
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=1210904374.23707.178.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 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.