All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brendan Cully <brendan@cs.ubc.ca>
To: xen-devel@lists.xensource.com
Subject: [PATCH 0 of 5] Make checkpointing backwards compatible with older kernels
Date: Fri, 12 Jan 2007 15:03:07 -0700	[thread overview]
Message-ID: <patchbomb.1168642987@ventoux.cs.ubc.ca> (raw)

This set of patches makes checkpointing backwards compatible with
older kernels. Checkpointable kernels now create a xenstore entry
called "control/feature-resumable" which xc save -c checks before
attempting to checkpoint a domain.

It also writes a new SIF_RESUMABLE flag into the suspend record,
which xc_linux_restore uses to decide whether it is safe to set the
hypercall return value. Although pre-checkpoint linux images ignore
the return value, I've heard that solaris bails out if the result is
anything but 0. Another possibly simpler strategy would be to flip the
return values, so 1 means the call is resuming in the source domain
and 0 means it is in a new domain and must reconnect. This is what
older kernels (that are only ever restored in a new domain) expect
anyway.

             reply	other threads:[~2007-01-12 22:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-12 22:03 Brendan Cully [this message]
2007-01-12 22:03 ` [PATCH 1 of 5] Advertise resumability feature in guest kernel Brendan Cully
2007-01-12 22:03 ` [PATCH 2 of 5] Disallow xm save -c unless the guest advertises that it is resumable Brendan Cully
2007-01-12 22:03 ` [PATCH 3 of 5] Add SIF_RESUMABLE flag to tell restore that a guest " Brendan Cully
2007-01-12 22:03 ` [PATCH 4 of 5] Set SIF_RESUMABLE flag in suspend Brendan Cully
2007-01-12 22:03 ` [PATCH 5 of 5] Do not set suspend return value unless SIF_RESUMABLE is set Brendan Cully
2007-01-13  9:28 ` [PATCH 0 of 5] Make checkpointing backwards compatible with older kernels Keir Fraser
2007-01-13  9:32 ` Keir Fraser

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=patchbomb.1168642987@ventoux.cs.ubc.ca \
    --to=brendan@cs.ubc.ca \
    --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.