From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id A32AFC43458 for ; Thu, 2 Jul 2026 06:02:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To: Content-Transfer-Encoding:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=96Z1Y5OhhvyQQIN/hKvuFMOzqQCu4hfBdjv68ntYyTU=; b=uyVKu7DDZ8tNEHlL47CrTbD+6Q /zbxnl28hihi9+/jRT21dN32qAFgPHK4ya2nLtUU4II/uEc/L6H3d1YyYgW7rAMbpsD41Wfj6G4ov aYGmFUGV6s6nHYxFbwx4BGLYzrlbwY9w8hM8B3FE9yc/HxsIuuDWDdXzUm4Hkg2Xo3RucLy3gTz0u an+miVvBfeJW4lPWY3YlmlCUluNAj8ainZNwe7CbNKxQH8igFJD23flT9wI4i308Txh9FMFE7e+2s Z/2yK9jMzKx/jX9W7qO5dK5unAgOd67w4PzoZjJhsp6CJEc3WhTkqfJW8WZN7amokCp+AkyCQUY4m tx5yj7xA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1wfAV9-00000003cQc-3gGR; Thu, 02 Jul 2026 06:02:19 +0000 Received: from mailgw.kylinos.cn ([124.126.103.232]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1wfAV7-00000003cPy-0R8o for kexec@lists.infradead.org; Thu, 02 Jul 2026 06:02:19 +0000 X-UUID: 8d258c1875db11f1aa26b74ffac11d73-20260702 X-CID-P-RULE: Release_Ham X-CID-O-INFO: VERSION:1.3.12,REQID:287a4c8e-ee83-4e0f-b6f7-06d0ac3634b1,IP:0,U RL:0,TC:0,Content:6,EDM:0,RT:0,SF:0,FILE:0,BULK:0,RULE:Release_Ham,ACTION: release,TS:6 X-CID-META: VersionHash:e7bac3a,CLOUDID:3255ca91ae41ae51a66dd66f7df0cd73,BulkI D:nil,BulkQuantity:0,Recheck:0,SF:80|81|82|83|102|136|850|865|898,TC:nil,C ontent:4|15|50,EDM:-3,IP:nil,URL:1,File:nil,RT:nil,Bulk:nil,QS:nil,BEC:nil ,COL:0,OSI:0,OSA:0,AV:0,LES:1,SPR:NO,DKR:0,DKP:0,BRR:0,BRE:0,ARC:0 X-CID-BVR: 2,SSN|SDN X-CID-BAS: 2,SSN|SDN,0,_ X-CID-FACTOR: TF_CID_SPAM_SNR,TF_CID_SPAM_ULS X-CID-RHF: D41D8CD98F00B204E9800998ECF8427E X-UUID: 8d258c1875db11f1aa26b74ffac11d73-20260702 X-User: duanchenghao@kylinos.cn Received: from localhost [(10.44.16.150)] by mailgw.kylinos.cn (envelope-from ) (Generic MTA with TLSv1.3 TLS_AES_256_GCM_SHA384 256/256) with ESMTP id 1658455910; Thu, 02 Jul 2026 14:02:05 +0800 Date: Thu, 2 Jul 2026 14:02:02 +0800 From: Chenghao Duan To: Pasha Tatashin Cc: Alexander Graf , "Andersen, Tycho" , Anthony Yznaga , Baolu Lu , David Hildenbrand , David Matlack , "Heyne, Maximillian" , James Gowans , Jason Gunthorpe , Mike Rapoport , Pankaj Gupta , Pratyush Yadav , Praveen Kumar , Vipin Sharma , Vishal Annapurve , "Woodhouse, David" , Luca Boccassi , Samiullah Khawaja , Jork Loeser , linux-mm@kvack.org, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, jianghaoran@kylinos.cn, duanchenghao@kylinos.cn Subject: Re: [Hypervisor Live Update] Notes from June 1, 2026 Message-ID: <20260702060202.GA78893@chenghao-pc> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.9.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20260701_230217_450992_3E1A2350 X-CRM114-Status: GOOD ( 28.59 ) X-BeenThere: kexec@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "kexec" Errors-To: kexec-bounces+kexec=archiver.kernel.org@lists.infradead.org On Sun, Jun 07, 2026 at 12:06:01PM -0400, Pasha Tatashin wrote: > Hi everybody, > > Here are the notes from the Hypervisor Live Update call that happened on > Monday, June 1. Thanks to everybody who was involved! > > These notes are intended to bring people up to speed who could not > attend the call as well as keep the conversation going in between > meetings. > > ----->o----- > LPC 2026 Call for Proposals > > The Call for Proposals for the Live Update Microconference at LPC 2026 > is officially open. Please submit your topics and proposals before the > deadline on July 24th. > > https://lore.kernel.org/all/ahcc3Qyuy7Oy03Iq@plex > > ----->o----- > KHO Xarray Implementation & Core Data Structures > > Pratyush is collaborating with Mike on a KHO fallback allocation > strategy for memblock. Alongside this, Pratyush is designing a > serialized, sparse "KHO Xarray" data structure to lift current mapping > restrictions across all three memfd types (shared, hugeTLB, and > guest_memfd). By allowing runtime page faults and allocation tracking > post-preservation, this avoids flat vmalloc array scalability > limitations. > > Potential wider use cases for the KHO Xarray were discussed: > - MSHV sparse bitmap tracking. > - IOMMU page table tracking (Samiullah will evaluate domain/device tree > association fit). > - PCI/VFIO sparse tracking via Bus/Device/Function (BDF) key spaces. > > Slab/Cache Preservation vs. Linked Blocks: > David Matlack noted that using an Xarray page per PCI device would be > too expensive given their small struct sizes. Pratyush suggested > preserving slab caches via dedicated kmem_cache flags to manage small, > arbitrary allocations. As an immediate alternative, Pasha's ongoing LUO > limits refactor series introduces a highly compact block-linked list > structure optimized for runtime file/session tracking. David Matlack > will review if this fits the PCI core tracking requirements. > > ----->o----- > LUO Limit Removal & PCI Core Status > > LUO Refactor: Pasha is updating the LUO series to address Pratyush's > comments (primarily renaming iterator functions) and plans to send out > v2 shortly. Given that LUO is not yet in fleet production, the group > agreed to fast-track this into the upcoming merge window to align with > systemd's fdstore integration. > > PCI Core v6: David Matlack sent out v6 incorporating two critical fixes > spotted by Sachiko regarding get/put semantics and double-retrieval > failures. Review tags from the live update team are needed to help > secure Bjorn's Ack once he returns from vacation next week. > > ----->o----- > IOMMU Persistence & Process Memory > > IOMMU v3: Samiullah is addressing recent review feedback on the IOMMU > persistence series and intends to post v3 by the end of this week. The > associated development roadmap document has received positive > stakeholder attention. > > CRIU & vm_splice: Maximilian's investigation into optimizing vm_splice > for copy-less data preservation remains deferred but remains in the > pipeline, with potential future collaboration with Google's tmpfs splice > efforts. I’ve also been researching a combination solution integrating CRIU and KHO. My approach stores all image data dumped by CRIU into memfd, then persists those memfd objects via KHO/LUO. I’ve reviewed the historical meeting notes and would like to clarify: does the CRIU solution discussed in the meetings aim to save the full set of a process’s metadata and data, or only the anonymous memory and shared memory allocated during the process runtime? Chenghao > > ----->o----- > guest_memfd Enlightenment & VMM Documentation > > Tarun debriefed the community on his upstream presentation regarding the > initial guest_memfd preservation patch series (currently covering fully > shared mappings with page-sized folios). > > Key design and architecture alignments include: > - VM File Association: guest_memfd requires an active 'struct kvm' > context to be retrieved. VMMs must preserve the parent VM file > alongside guest_memfd, using LUO tokens to re-link them on the > incoming kernel path. This sets the stage for future private > mapping/secure EPT table tracking. > - Relaxed Fault Logic: The group agreed to drop strict upfront pre-fault > checks. Instead, standard runtime page-fault semantics will apply. If > a guest page fault occurs post-preservation, it will bubble up via > standard KVM_RUN ioctl exits to the VMM, which can safely pause vCPUs > and retry the fault post-kexec. > - Centralized VMM Documentation: Pasha and David Matlack proposed > creating a centralized guide under live_update/vmm detailing the > overall live update flow, timing constraints, and subsystem > requirements to assist external QEMU and VMM developers. > > ----->o----- > Next meeting will be on Monday, June 15 at 8am PDT (UTC-7), everybody is > welcome: https://meet.google.com/rjn-dmzu-hgq > > Note: I am going to be traveling on June 15th, David Matlack is going to > be hosting it. > > Topics for the next meeting: > - Presentation of VFIO roadmap (Vipin and David Matlack) > - Status of KHO Xarray development and slab preservation feasibility > - Review of PCI core changes v7 and upstream merge coordination > - IOMMU persistence v3 review feedback > - Detailed review of guest_memfd v2 and VMM interaction documentation > - Review and coordination of LPC 2026 Microconference topic submissions > - later: KHO support for Confidential VMs including page table > preservation and pinning > - later: versioning support for luod to negotiate > - later: KHO enlightenment for ASI > - later: update on PCI preservation series and next steps > - later: testing methodology to allow downstream consumers to qualify > that live update works from one version to another > - later: reducing blackout window during live update, including deferred > struct page initialization > > Please let me know if you'd like to propose additional topics for > discussion, thank you!