From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pl1-f200.google.com (mail-pl1-f200.google.com [209.85.214.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D69003D301E for ; Mon, 17 Aug 2026 14:37:32 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.214.200 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786977454; cv=none; b=QE5ZBjcMS6N14dGbZ8qZ4bWueEzNtAsWExoAY4+Wf6muGi0/p1rOo9fCUxoTnyjJEJ6qNL3zsY1yAQe0LhhHhj2QKh5o/pThCwDKNolR4bHQrdbLIJFQYxjFJiXxMkl+KWwNUJV4V6niYUawE5vCOt1r6C/Vu/AdAXKepnuSisA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786977454; c=relaxed/simple; bh=lerb0gKuqV7hyiHwD7tAixcPyrYjaXEE+RDGLUvUXEo=; h=Date:In-Reply-To:Mime-Version:References:Message-ID:Subject:From: To:Cc:Content-Type; b=VcUvlaWUlss4S9leLShbUjEhfNkuErCwWgzXfWlOhSnQjjDP4wjd3/KHGfvX9qtlfbvckuc/llr3yhHwuCA5b0VY9SZXG+PYPSHFrjpPjYp2estx2YOjGqcKiwOK5ltKBgMiHh4UH7pXQyzHyc5kL3P5CS9GL9lWkqqDrwF0NrY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=google.com; spf=pass smtp.mailfrom=flex--seanjc.bounces.google.com; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b=ts+1GB3A; arc=none smtp.client-ip=209.85.214.200 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=google.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=flex--seanjc.bounces.google.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="ts+1GB3A" Received: by mail-pl1-f200.google.com with SMTP id d9443c01a7336-2ccd1958e8fso55598315ad.2 for ; Mon, 17 Aug 2026 07:37:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20251104; t=1786977451; x=1787582251; darn=vger.kernel.org; h=content-type:cc:to:from:subject:message-id:references:mime-version :in-reply-to:date:from:to:cc:subject:date:message-id:reply-to :content-type; bh=xbnAp7y/AgCt9+7CBSjoILDuat4y2Kbyd9OVnJGDiZs=; b=ts+1GB3AGdgTNHtaG3eA7hS1Dy7WztPkLYICC+LAGAIhZAIWlkhcVYSptrESkFnBQR aJVlcIdgRkFxM5f82E1Vq0PU9ceXSOtWn7NxQdN9Fvg9dnV1eZx1gFUDhSrfVKZIxviE 5tHEQCX8jnAv/PSg1grT3rb3CbiMVQOlXJtiTONQMT3W7XJhW6/1037x8REPOFtOknqR IVu4P5c/BvAy984Ureu8X/GxP//iEei384gFFSsH4/oimp6MtM9WQrJoFW66e2NmR3Bv LvAXjdZxXnMy7j+GZC0Cch8+DmOWf1+oZlZvxQ+gMmNmMTJ3+KHLVcOd+LNjbtI/GFux xcdA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1786977451; x=1787582251; h=content-type:cc:to:from:subject:message-id:references:mime-version :in-reply-to:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to:content-type; bh=xbnAp7y/AgCt9+7CBSjoILDuat4y2Kbyd9OVnJGDiZs=; b=ZP6LoDLlfiCNlVNn2L8yi52BOr1ygy1fZiUgio3+5u47Xy4xI+naEVcY7SascujBS2 8dM+QKWDr0ZNbb7swcU8Tbsv3bVFlkqf2kxKl0AXUDHMf6Nor6EUkZJ04ZsKjYMMWqMa zWlgLM+PMUisJKy8jvbzT7RgEjPdziBbwS4ZqdX9MeRmijby+08L8aWPo/G9TBS7MEMK tQF0sLRzww4YoZXtG4CXAViGxzyw2KwMy9+DKWaSTLklpxiNhAAlHf/Fq3ZEH5DFbWkH Jh9RmdQUDWUT4psSbe3OfEP4NGcyXyaoKiTedgXKOwziIM7TIaBJ7I1xC0hJyvNTKZc0 xZqA== X-Forwarded-Encrypted: i=1; AHgh+RpDTns4fdYbgz28s4BiHTKsU4dItbxgBELCncPuW2K8kTutO7DTR/2wINk0yfcT8o+ateFpFQX7jQumLio=@vger.kernel.org X-Gm-Message-State: AOJu0YwQBOI/6G0PyyVFNZdFcUj8hq71WB81hVu2hRoWUn0qVELNeTRw Ie3Zuj6WPYb/zeUY19gJjBCLmr85CNYGnPbgNFATDple6HSfjDIB+W7h9GVIMwfimM5FA5lrX/q xNViIXg== X-Received: from plbmo3.prod.google.com ([2002:a17:903:a83:b0:2c7:702a:36a4]) (user=seanjc job=prod-delivery.src-stubby-dispatcher) by 2002:a17:903:b0b:b0:2cf:9347:f445 with SMTP id d9443c01a7336-2d3b0c7ae46mr283430775ad.10.1786977451095; Mon, 17 Aug 2026 07:37:31 -0700 (PDT) Date: Mon, 17 Aug 2026 07:37:30 -0700 In-Reply-To: <2vxzqzjz1x5f.fsf@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 References: <20260728121138.1103610-1-tarunsahu@google.com> <20260728121138.1103610-6-tarunsahu@google.com> <2vxzpkzo51wg.fsf@kernel.org> <2vxzik5f311e.fsf@kernel.org> <2vxzqzjz1x5f.fsf@kernel.org> Message-ID: Subject: Re: [PATCH v4 05/11] KVM: LUO: Support VM preservation across live updates From: Sean Christopherson To: Pratyush Yadav Cc: Tarun Sahu , ackerleytng@google.com, fuad.tabba@linux.dev, Andrew Morton , dmatlack@google.com, Shuah Khan , Jonathan Corbet , david@redhat.com, Pasha Tatashin , sagis@google.com, Paolo Bonzini , Mike Rapoport , Alexander Graf , linux-kselftest@vger.kernel.org, andre.przywara@arm.com, michael.roth@amd.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, will@kernel.org, vannapurve@google.com, maz@kernel.org, fvdl@google.com, kvm@vger.kernel.org, oliver.upton@linux.dev, kvmarm@lists.linux.dev, alexandru.elisei@arm.com, skhawaja@google.com, aneesh.kumar@kernel.org, linux-doc@vger.kernel.org, David Hildenbrand , yan.y.zhao@intel.com, kexec@lists.infradead.org, suzuki.poulose@arm.com Content-Type: text/plain; charset="us-ascii" On Sat, Aug 15, 2026, Pratyush Yadav wrote: > On Wed, Aug 12 2026, Sean Christopherson wrote: > > On Wed, Aug 12, 2026, Pratyush Yadav wrote: > >> This is ABI between kernels. It needs to be stable-ish so you can move > >> from one kernel version to another. At the same time, unlike userspace > >> ABI, it can change. > > > > Uh, yeah, so KVM has been managing such immutable ABI for practically its entire > > existence. KVM's save/restore uAPI has exactly what you're describing: serialization > > ABI that needs to be backwards and forwards compatible between different kernels > > in order to support both upgrade and rollback scenarios via live migration. > > I think there is a slight difference between KVM's save/resture uAPI and > live update's ABI. With KVM's uAPI, you need to maintain strict > backwards compatibility because userspace reads what you output. So if > you change the layout, userspace will interpret it wrong and might > break. > > With live update, the ABI never gets to userspace. It is used to talk > between kernels directly. So if you do break that, your userspace keeps > working fine, you just might not be able to live update to the > incompatible kernel. > > So with live update, we don't need to keep backwards compatibility in > the ABI forever. Of course, it is good to minimize changes, but we have > more freedom to change it. Ah. So this is the heart of the disconnect. I very strongly disagree with the statement that live update doesn't need to support backwards compatibility. I can totally believe that the folks working on live update are ok breaking backwards compatibility because their use cases are "fine" with such breakage. And I can also believe live update as an upstream kernel feature being developed by those same folks is also ok with breaking backwards compatibility. But with my upstream KVM maintainer hat on, I am not ok with that. I did not agree to support a world where KVM is allowed to break backwards compatibility, so long as it's done "carefully" or whatever. If y'all want to deal with the resulting complexity, that's fine by me, but you'll be doing it without KVM. I totally understand that exploratory work and initial development is best done in private and/or in a small working groups. But decisions that will significantly impact multiple subsystems need to be made *with* those subystems. I mean, obviously it's possible to make a decision in a small group and then "publish" the result later, but then as is happening here, the community and subsystem maintainers like me may refuse to play ball if they disagree. To be very clear, for any KVM live update support that doesn't guarantee backwards compatibility (allowing that bugs happen), a very firm: NAK