From: Paul Durrant <paul.durrant@citrix.com>
To: xen-devel@lists.xensource.com
Cc: paul.durrant@citrix.com
Subject: [PATCH 0 of 4] Support for VM generation ID save/restore and migrate
Date: Fri, 16 Dec 2011 14:54:33 +0000 [thread overview]
Message-ID: <patchbomb.1324047273@cosworth.uk.xensource.com> (raw)
This patch series adds support for preservation of the VM generation ID buffer address in
xenstore across save/restore and migrate, and also code to increment the value in all cases
except for migration.
Patch 1 modifies the guest ro and rw node creation to an open coding style and cleans up some
extraneous node creation.
Patch 2 modifies creation of the hvmloader key in xenstore and adds creation of a new read/write
hvmloader/generation-id-addr key.
Patch 3 changes hvmloader to use the new key (as opposed to the old data/generation-id key). Note
that it is safe to apply this patch independently of the others but it logically belongs at this
position in the series.
Patch 4 adds the infrastructure to save and restore the VM generation ID address in xenstore and
the code to increment the value.
next reply other threads:[~2011-12-16 14:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 14:54 Paul Durrant [this message]
2011-12-16 14:54 ` [PATCH 1 of 4] Open code rw and ro node creation Paul Durrant
2011-12-16 14:54 ` [PATCH 2 of 4] Add hvm specific ro and rw nodes Paul Durrant
2011-12-16 14:54 ` [PATCH 3 of 4] Re-name xenstore key used to save VM generation ID buffer address Paul Durrant
2011-12-16 14:54 ` [PATCH 4 of 4] VM generation ID save/restore and migrate Paul Durrant
2012-01-06 9:35 ` [PATCH 0 of 4] Support for " Paul Durrant
2012-01-10 15:58 ` Ian Jackson
2012-01-10 16:35 ` Paul Durrant
-- strict thread matches above, loose matches on Subject: below --
2011-12-16 14:45 Paul Durrant
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.1324047273@cosworth.uk.xensource.com \
--to=paul.durrant@citrix.com \
--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.