From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ferdinand Brasser <ferdinand.brasser@trust.cased.de>
Cc: mihai.bucicoiu@trust.cased.de, xen-devel@lists.xen.org
Subject: Re: [HotSwap] Live Update for Xen
Date: Fri, 17 Jan 2014 13:28:04 +0000 [thread overview]
Message-ID: <52D92FE4.9080504@citrix.com> (raw)
In-Reply-To: <1389964977.2099.3.camel@64bitDom0>
On 17/01/14 13:22, Ferdinand Brasser wrote:
> Dear all,
>
> My name is Ferdinand Brasser, research assistant at CASED/TU Darmstadt.
>
> Here at CASED, we have developed a live updating mechanism for Xen,
> which we call it HotSwap. Currently we have a prototype for Xen 4.2 and
> would like to know if there is any interest from the community to
> integrate our approach into Xen. If so, some advice on how to proceed is
> welcomed.
>
> Our approach to update Xen is - very high level - to load a complete new
> version of Xen at runtime and then transfer the state of the old version
> to the new one. Afterwards the execution is continued by the new
> version. We make use of Xen functions to disable all but one CPU and
> interrupts during the update process to keep the state consistent while
> transferring. We have evaluate our prototype with the result that the
> update process takes about 45ms on our test system.
>
> We hope you guys find this work interesting and we would be happy to
> work together with you to make our prototype a usable and reliable
> function of Xen.
>
> Regards,
> Ferdinand
Hello,
This looks like a fantastic area to be working in, and I am sure people
would be interested in playing with it
As far as how to proceed, your best bet would be to provide some code
and instructions, perhaps with a step-by-step guide for a demo?
~Andrew
next prev parent reply other threads:[~2014-01-17 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 13:22 [HotSwap] Live Update for Xen Ferdinand Brasser
2014-01-17 13:28 ` Andrew Cooper [this message]
2014-01-17 14:16 ` Ian Campbell
2014-02-18 16:44 ` Dario Faggioli
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=52D92FE4.9080504@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=ferdinand.brasser@trust.cased.de \
--cc=mihai.bucicoiu@trust.cased.de \
--cc=xen-devel@lists.xen.org \
/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.