All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: David Knight <dongwei.net@pku.edu.cn>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: A question about "suspend-record frame number"
Date: Sat, 21 Feb 2009 20:43:39 -0800	[thread overview]
Message-ID: <C5C617FB.2ADA%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <49A02F06.3070801@pku.edu.cn>

The suspend-record provides information from the suspended guest to
xc_domain_save/restore in the toolstack, and then back to the restored
guest. You can't just do xc_domain_shutdown() from the tools because a PV
guest has to prepare itself for save/restore, and it wouldn't get the chance
to do that in that case. The suspend_and_state() got sped up a lot for
guests which support suspend notification via an event channel (rather than
going via xenstore, which is 100s of milliseconds slower typically).

 -- Keir


On 21/02/2009 08:42, "David Knight" <dongwei.net@pku.edu.cn> wrote:

> Dear friends:
> 
> in xc_domain_save.c, there is a suspend-record frame number which is
> stored in the first vcpu's edx register. What the major use of this
> "suspend-record frame number". Why this frame number is store there?
> 
> I want to replace the suspend_and_state with xc_domain_shutdown because
> the former one is much slower. But after I replaced the funcion, that
> frame number was lost. What if I ignore the error and omit the
> corresponding code in xc_domain_restore.c?? Thanks.
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

      reply	other threads:[~2009-02-22  4:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-21 16:42 A question about "suspend-record frame number" David Knight
2009-02-22  4:43 ` Keir Fraser [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=C5C617FB.2ADA%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=dongwei.net@pku.edu.cn \
    --cc=xen-devel@lists.xensource.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.