From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dario Faggioli Subject: Re: [HotSwap] Live Update for Xen Date: Tue, 18 Feb 2014 17:44:05 +0100 Message-ID: <1392741845.32038.569.camel@Solace> References: <1389964977.2099.3.camel@64bitDom0> <1389968194.6697.108.camel@kazak.uk.xensource.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3275991284384673761==" Return-path: In-Reply-To: <1389968194.6697.108.camel@kazak.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: Ferdinand Brasser , mihai.bucicoiu@trust.cased.de, xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org --===============3275991284384673761== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-M6cm2ic09lJ/+E04T+Oc" --=-M6cm2ic09lJ/+E04T+Oc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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, > >=20 > > My name is Ferdinand Brasser, research assistant at CASED/TU Darmstadt.= =20 > >=20 > > 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 i= s > > welcomed. > >=20 > > Our approach to update Xen is - very high level - to load a complete ne= w > > version of Xen at runtime and then transfer the state of the old versio= n > > 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.=20 >=20 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. >=20 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 --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-M6cm2ic09lJ/+E04T+Oc Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEABECAAYFAlMDjdUACgkQk4XaBE3IOsQ1YQCfa5vVeBKWLNwgmIwQEylApbAn Kj0AoKp/BvB4X/+yTEdgo7o5aazjtXtp =7DRj -----END PGP SIGNATURE----- --=-M6cm2ic09lJ/+E04T+Oc-- --===============3275991284384673761== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============3275991284384673761==--