Message ID | a92287c03fed310e08ba40063e370038569b94ac.camel@infradead.org (mailing list archive) |
---|---|
Headers | show
Return-Path: <SRS0=pEfl=3T=lists.xenproject.org=xen-devel-bounces@kernel.org> Received: from mail.kernel.org (pdx-korg-mail-1.web.codeaurora.org [172.30.200.123]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 8353D112B for <patchwork-xen-devel@patchwork.kernel.org>; Thu, 30 Jan 2020 16:14:45 +0000 (UTC) Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 53B9D20707 for <patchwork-xen-devel@patchwork.kernel.org>; Thu, 30 Jan 2020 16:14:45 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="tqztyl1+" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 53B9D20707 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=infradead.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=xen-devel-bounces@lists.xenproject.org Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.89) (envelope-from <xen-devel-bounces@lists.xenproject.org>) id 1ixCRK-00041D-O3; Thu, 30 Jan 2020 16:13:10 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.89) (envelope-from <SRS0=ZPhi=3T=bombadil.srs.infradead.org=batv+316c8ce85392a3425e94+6003+infradead.org+dwmw2@srs-us1.protection.inumbo.net>) id 1ixCRJ-000418-2N for xen-devel@lists.xenproject.org; Thu, 30 Jan 2020 16:13:09 +0000 X-Inumbo-ID: 610c9084-437b-11ea-8396-bc764e2007e4 Received: from bombadil.infradead.org (unknown [2607:7c80:54:e::133]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id 610c9084-437b-11ea-8396-bc764e2007e4; Thu, 30 Jan 2020 16:12:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20170209; h=Mime-Version:Content-Type:Date:Cc:To: From:Subject:Message-ID:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=7Pl1euam4viv9alO2QUlikckgONIfiY6HBbf8PLqOHc=; b=tqztyl1+mAI7HUW34hBeEUxnT0 sCPKZvHtgV2e7ZrUB5Vj8M3R7Ef6zmKH7WbdqzInzwJn5fKaF/CLt1uBEbecCZG0WPq1HELLpUnjK nKLZQgoU5IoK0nGgPYcYAQ88v2Ut5Ur4HBDoN45fhjjp0MOPHYLNXrctp1ydHOHImgHItffFJk/1O LLYmx3fGotW0O0GIR76o56jklsBJMbdTc2sCBpzED12gyOYEVblyvcUxrE/Ny2HkATKjc9vZW7MB8 D823ayfLAOQaON3n/mOE4566kN6LL8tMKJgO/3wnagbOubm76VYsRU/AMPQW041Fe76JnOkaJBW+N /3k72TAw==; Received: from 54-240-197-236.amazon.com ([54.240.197.236] helo=freeip.amazon.com) by bombadil.infradead.org with esmtpsa (Exim 4.92.3 #3 (Red Hat Linux)) id 1ixCR6-0004Oi-3X; Thu, 30 Jan 2020 16:12:56 +0000 Message-ID: <a92287c03fed310e08ba40063e370038569b94ac.camel@infradead.org> From: David Woodhouse <dwmw2@infradead.org> To: Xen-devel <xen-devel@lists.xenproject.org> Date: Thu, 30 Jan 2020 16:12:52 +0000 X-Mailer: Evolution 3.28.5-0ubuntu0.18.04.1 Mime-Version: 1.0 X-SRS-Rewrite: SMTP reverse-path rewritten from <dwmw2@infradead.org> by bombadil.infradead.org. See http://www.infradead.org/rpr.html Subject: [Xen-devel] [RFC PATCH v3 0/22] Live update: boot memory management, data stream handling, record format X-BeenThere: xen-devel@lists.xenproject.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Xen developer discussion <xen-devel.lists.xenproject.org> List-Unsubscribe: <https://lists.xenproject.org/mailman/options/xen-devel>, <mailto:xen-devel-request@lists.xenproject.org?subject=unsubscribe> List-Post: <mailto:xen-devel@lists.xenproject.org> List-Help: <mailto:xen-devel-request@lists.xenproject.org?subject=help> List-Subscribe: <https://lists.xenproject.org/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xenproject.org?subject=subscribe> Cc: Stefano Stabellini <sstabellini@kernel.org>, Julien Grall <julien@xen.org>, Wei Liu <wl@xen.org>, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>, George Dunlap <George.Dunlap@eu.citrix.com>, Andrew Cooper <andrew.cooper3@citrix.com>, Varad Gautam <vrd@amazon.de>, paul@xen.org, Ian Jackson <ian.jackson@eu.citrix.com>, Hongyan Xia <hongyxia@amazon.com>, Amit Shah <aams@amazon.de>, Roger Pau =?iso-8859-1?q?Monn=E9?= <roger.pau@citrix.com> Content-Type: multipart/mixed; boundary="===============5096036330932177202==" Errors-To: xen-devel-bounces@lists.xenproject.org Sender: "Xen-devel" <xen-devel-bounces@lists.xenproject.org> |
Series |
Live update: boot memory management, data stream handling, record format
|
expand
|
David Woodhouse writes ("[RFC PATCH v3 0/22] Live update: boot memory management, data stream handling, record format"): > Now with added documentation: > http://david.woodhou.se/live-update-handover.pdf I had a look at this. I didn't read the patches in detail, but I did read all of [RFC PATCH v3 05/22] Add KEXEC_TYPE_LIVE_UPDATE It seems plausible to me. This seems a new and interesting way of updating Xen underneath running guests. BUT I am not an expert on the migration code. I hope Andrew Cooper will be able to comment... Regards, Ian.