From: Dario Faggioli <dario.faggioli@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Ferdinand Brasser <ferdinand.brasser@trust.cased.de>,
mihai.bucicoiu@trust.cased.de, xen-devel@lists.xen.org
Subject: Re: [HotSwap] Live Update for Xen
Date: Tue, 18 Feb 2014 17:44:05 +0100 [thread overview]
Message-ID: <1392741845.32038.569.camel@Solace> (raw)
In-Reply-To: <1389968194.6697.108.camel@kazak.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1822 bytes --]
Hey,
[I always wanted to reply to this thread, but then it slipped over and
over, up to now!]
On ven, 2014-01-17 at 14:16 +0000, Ian Campbell wrote:
> On Fri, 2014-01-17 at 14:22 +0100, 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.
>
Wow, 45ms is certainly something bearable for this kind of
operation! :-P
> This sounds pretty cool. I think everyone would be interested in hearing
> a bit more about it and in seeing the code.
>
I agree... this would be a really great feature to have!
So, any news? Any update? Any plan on following Ian's suggestions to
--at least try to-- upstream it?
Thanks and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2014-02-18 16:44 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
2014-01-17 14:16 ` Ian Campbell
2014-02-18 16:44 ` Dario Faggioli [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=1392741845.32038.569.camel@Solace \
--to=dario.faggioli@citrix.com \
--cc=Ian.Campbell@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.