From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=209.85.214.175 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1794337338; b=zHN8f5dyGirViAXfckScx1PLrZ6ANHXHsPpOUj48vIZOZQ+raSzz249DvLwdFFAlx63h eD5iuri77beqwjihS295UrVqbRvN653XjA6NDlOO/JM52wYMo1XaWywYregtQpIkBCrYC D5hR8mLL5QOCRSpLXxwzEWIadCsmvRIAhJkRf7h1hcsNqZlW5iOhICDE98WD4Bq96LPY5 ShZLgMl5vnuOyOyOzfl6PpVMPvdlndI0WDEaJTNV/M7N2efT2pIbxTOghxjXf0X33ba22 tqoDfeO5saLImBIOpW8RuBkJPGXgZWgcYziYjcz9mJ6yyeBq3CZ9O0FPtYRDnQABSOA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1794337338; h=DMARC-Filter:Received:DKIM-Signature:X-Google-DKIM-Signature: X-Forwarded-Encrypted:X-Gm-Message-State:X-Gm-Gg:X-Received:Received: Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; bh=Rc92iNBDR3TpfE1Wb0FPlqB33KW4gheFc7Efbj9D4zA=; b=2solB7YekMxhbGumJdDiDFXDOE7dWUipWlpVuAtDLlg5y58Yg9kugPv3u6fzYbOf6Org /JVYY1y01M/gtL4vJ8/dJJkr4/UoOb1M6tLR3jeEzfMLNiS0CbYTPamH6s8FV+cxmy4Vp 8rA5gkN4L/u49GUCn9MDE30kKAqvnpRW85lY066yL6VzsCLeUIoZ4dV5s5QjArCzo4CAm h07DijksSvUOLwQG9DP8+sqjSsNqDhbJApohcoyKy7gK+btqr0Hh5daPZHzgqHE7Wvvv8 KIITb3DCX3wHrTIgLoCsoPjpCNpXcPiFWRA16fMmN7nWL+pVUlF8Cvkf5gmonyb6Wdw== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=google.com; spf=pass smtp.mailfrom=google.com; dkim=pass header.d=google.com header.i=@google.com header.a=rsa-sha256 header.s=20260707 header.b=qO+JZOY4; arc=none smtp.remote-ip=209.85.214.175 Received: from mail-pl1-f175.google.com (mail-pl1-f175.google.com [209.85.214.175]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 749FA606A325 for ; Tue, 10 Nov 2026 19:02:18 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org 749FA606A325 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=google.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.a=rsa-sha256 header.s=20260707 header.b=qO+JZOY4 Received: by mail-pl1-f175.google.com with SMTP id d9443c01a7336-2ed3f563739so6855ad.0 for ; Tue, 10 Nov 2026 11:02:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20260707; t=1794337338; x=1794942138; darn=vger.kernel.org; h=in-reply-to:content-disposition:content-type:mime-version :references:message-id:subject:cc:to:from:date:from:to:cc:subject :date:message-id:reply-to:content-type; bh=Rc92iNBDR3TpfE1Wb0FPlqB33KW4gheFc7Efbj9D4zA=; b=qO+JZOY4XThqw7+Njn/UYcPIm7ZmOo3MiW+t20KLHVibC+4UuvF6oB0AUlTA5C+Kz5 8bfjmyokmdpWkvtsirhnzw3yZxnpal6DZh4ctcbQuikaRqogrXN0Fg5MkiFa8k3d0ZdV 6yHbQWhuX6VDHoqmvKkSeQVgoE06RF1Rh46qLj1+0lLUGq1fvXjYSdZ/wzPg2gJdk5mk ri70ob/7Sp1bFE8dTCuvgv7LeNHaYdC667uwY7mMMz+afixjYSayD4a69OskUXzmcrNu AXpWknVWVYiL/bjDdQg7mYlZxD1abxJRY2WRtUvcVfj93a3zD+lUsfOsoLuWUOnWKoUl Z+Tg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1794337338; x=1794942138; h=in-reply-to:content-disposition:content-type:mime-version :references:message-id:subject:cc:to:from:date:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=Rc92iNBDR3TpfE1Wb0FPlqB33KW4gheFc7Efbj9D4zA=; b=Mx5VxzwwT4T5lMafNV/x2S7a/Zptpi1M4VZc82cME56GB52yBdhJ+doZIwScVjxZC0 NeO2S7e6dloSAqpLYwCfB3ZoGe3GnYPu9fL90tdgcTGnZVy8g9SHLzmm0EampUQhaVLX lBbJw72NAF8BhnrFO8fHUbHOTTklgXd9PY3hqDYUYMOauPT/bZKCp/Xspryzt3WCUDeo +PKQINmfVkjhnDwMqZ5CTAuRz1Pit5+apbTM4r75jO6ccqBsTO53N40XHpgY2gE0YG3L zh59FcJpUWxoTf8IEj5cQ3zVpkfbWHOop/Qee4VNw/QVaCmKLIuGFDZu1GLWPrfaAX9u kb4g== X-Forwarded-Encrypted: i=1; AL+hErFau8S46snqjXLCgzzOYMIXhL/aGvQ4q9QWQoxQQWUjtaiavnnVoRJWOgAWiIiH0vTtkxo=@vger.kernel.org X-Gm-Message-State: APuU4Z/672vaWfsijs1Wcih0aRQSSBMXW+sMvbIGKN5jnJgfE5pN+6XF nbrsVOi1k2U6U7TUqRxKxLuplu78hqxt6peugKSSw9FC9XwD34vX4JP1rPQVmBDXAw== X-Gm-Gg: AYBFou1WTZpDeJmUg2vPAWTS4r+QYAc+qWBL/ZWzJZrI4qY9Stha12RblHkl0iSkLa6 v+jt0LgrBypkR8s8HzfFs8D4N7mApzxlvhm0K4JUZvS88sqEGYTaT8JQTQv+3nMfjwwBz5U3mef cMsXdV+lshGNClkg4Zj/wi8SsPzRoLJGPnZQxMRD+ryxIxIQs7a9eOBkDl7HvXAIqDPzsWwPnc+ 1yCQEgsqyMmvy41PlpzoNvB1Ovoh2YMMOYh2cxHgYco2O9rjXvSZhugW2OVpSvJRXJskNE1YTYl Q8pkLiHyxNiROs5hSxaVvvNGRcsF1LoP+v2xWARbv6S27lJmY9YWnPek4bwyBIIMzrxojn4s1UN SXr+G5dPGTcKtJ69EaoG/ehdlHZjK/arAkWtLPsD9fuPqlLoIvsymAEwovH45y/f7IfbyoJZglk NPZqKmT5c64ih5z6d6ShRa67uAm/GFg3VMWNluIHxwmQYYDVOuUkYIf2kAc1b01Zf56uh5mqyeN sCKyhGr8Bz7kmTKrdqQNSs9MEvkFLZjw2Zd/NA9GrEudj5yJYIrhSsNwC5PHFiT7pIFYV8yrHhX 50k+/gDP1R9I9H1PPRZZ4uVfJwdc6jsksVaAC6yfqSEQVXWcGxtut0W3cPdrw8dk X-Received: by 2002:a17:903:1b44:b0:2d5:db38:8010 with SMTP id d9443c01a7336-2edba3e2a10mr5113665ad.15.1794337336971; Tue, 10 Nov 2026 11:02:16 -0800 (PST) Received: from google.com (60.89.247.35.bc.googleusercontent.com. [35.247.89.60]) by smtp.gmail.com with ESMTPSA id 98e67ed59e1d1-3b17db31cafsm914394a91.3.2026.11.10.11.02.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 10 Nov 2026 11:02:15 -0800 (PST) Date: Tue, 10 Nov 2026 11:02:11 -0800 From: Vipin Sharma To: Samiullah Khawaja Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, kvm@vger.kernel.org, linux-mm@kvack.org, linux-kselftest@vger.kernel.org, linux-pci@vger.kernel.org, ajayachandra@nvidia.com, alex@shazbot.org, amastro@fb.com, ankita@nvidia.com, apopple@nvidia.com, bhelgaas@google.com, chrisl@kernel.org, christian.koenig@amd.com, corbet@lwn.net, dmatlack@google.com, graf@amazon.com, jacob.pan@linux.microsoft.com, jgg@nvidia.com, jgg@ziepe.ca, jrhilke@google.com, julianr@linux.ibm.com, kees@kernel.org, kevin.tian@intel.com, leon@kernel.org, leonro@nvidia.com, lukas@wunner.de, mattev@meta.com, michal.winiarski@intel.com, parav@nvidia.com, pasha.tatashin@soleen.com, praan@google.com, pratyush@kernel.org, rananta@google.com, rdunlap@infradead.org, rientjes@google.com, rodrigo.vivi@intel.com, rppt@kernel.org, saeedm@nvidia.com, schnelle@linux.ibm.com, skhan@linuxfoundation.org, vivek.kasireddy@intel.com, witu@nvidia.com, yanjun.zhu@linux.dev, yi.l.liu@intel.com Subject: Re: [PATCH v6 04/27] vfio/pci: Register a file handler with Live Update Orchestrator Message-ID: <20261110185305.GC519525.vipinsh@google.com> References: <20261102153656.1431701-1-vipinsh@google.com> <20261102153656.1431701-5-vipinsh@google.com> X-Mailing-List: kvm@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Fri, Nov 06, 2026 at 10:29:06PM +0000, Samiullah Khawaja wrote: > On Mon, Nov 02, 2026 at 07:36:33AM -0800, Vipin Sharma wrote: > > Register a live update file handler for vfio-pci device files. Add stub > > implementations of all required callbacks so that registration does not > > fail. Register it with both live update framework and PCI subsystem. > > > > This file handler will be extended in subsequent commits to enable a > > device bound to vfio-pci to run without interruption while the host is > > going through a kexec Live Update. > > > > Put this support behind a new Kconfig VFIO_PCI_LIVEUPDATE. Initial > > support is added for no-iommu model vfio-pci devices. > > > > Co-developed-by: David Matlack > > Signed-off-by: David Matlack > > Signed-off-by: Vipin Sharma > > --- > > MAINTAINERS | 1 + > > drivers/vfio/pci/Kconfig | 11 ++++ > > drivers/vfio/pci/Makefile | 1 + > > drivers/vfio/pci/vfio_pci.c | 11 +++- > > drivers/vfio/pci/vfio_pci_liveupdate.c | 75 ++++++++++++++++++++++++++ > > drivers/vfio/pci/vfio_pci_priv.h | 14 +++++ > > include/linux/kho/abi/vfio_pci.h | 28 ++++++++++ > > 7 files changed, 140 insertions(+), 1 deletion(-) > > create mode 100644 drivers/vfio/pci/vfio_pci_liveupdate.c > > create mode 100644 include/linux/kho/abi/vfio_pci.h > > > > diff --git a/MAINTAINERS b/MAINTAINERS > > index 5d1b58271989..167aa9d66ce8 100644 > > --- a/MAINTAINERS > > +++ b/MAINTAINERS > > @@ -28662,6 +28662,7 @@ F: Documentation/ABI/testing/debugfs-vfio > > F: Documentation/ABI/testing/sysfs-devices-vfio-dev > > F: Documentation/driver-api/vfio.rst > > F: drivers/vfio/ > > +F: include/linux/kho/abi/vfio_pci.h > > F: include/linux/vfio.h > > F: include/linux/vfio_pci_core.h > > F: include/uapi/linux/vfio.h > > diff --git a/drivers/vfio/pci/Kconfig b/drivers/vfio/pci/Kconfig > > index 296bf01e185e..e8285ad93a69 100644 > > --- a/drivers/vfio/pci/Kconfig > > +++ b/drivers/vfio/pci/Kconfig > > @@ -42,6 +42,17 @@ config VFIO_PCI_IGD > > and LPC bridge config space. > > > > To enable Intel IGD assignment through vfio-pci, say Y. > > + > > +config VFIO_PCI_LIVEUPDATE > > + bool "VFIO PCI support for Live Update in no-iommu mode" > > + depends on PCI_LIVEUPDATE && VFIO_NOIOMMU > > Can we handle this dependency in code instead of doing through > configs? Are there any build dependencies on noiommu? I can remove it but then by itself VFIO series will enable LIVEUPDATE irrespective of VFIO_NOIOMMU and it will just fail when someone tries to enable it. So, kconfig looks cleaner to me. Can your series modify this kconfig and add (VFIO_NOIOMMU || IOMMU_LIVEUPDATE)? Will that work for you?