From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pl1-f176.google.com (mail-pl1-f176.google.com [209.85.214.176]) (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 3A9E2481658 for ; Mon, 18 May 2026 14:01:38 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.214.176 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779112899; cv=none; b=o1YAcG8T/tki8RvZr9jxVir0ZAWxGxsk5A9eu5sMnfnPJBJJirXbabfg38QMcF49AjPeaboX+VKYE1d+p+XUfHVmXeaflgtrlo9jXdKmya9PCzfD5BvWTFU2c+xBbA+Mr1GcJ1098G9FhPxVPOcGbSseYdNlLN7wHd+uu6Dpbwc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779112899; c=relaxed/simple; bh=pDXXz1TH87s1IivcdxWzN8kqNDaLaW3x0g7egMGT/II=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=mxIGkncuf4erY2pPMreCyKrZYM2OlAB/5rYMKnKzCT5Vgx2lUgGCQjElfe9rccjTgNOqa2khmxB3qn1+0aqVNF7jIOOtURhM/KdhnTyQfgOFxy+Xts23fL+WmE5SDT+PXtkYeIua6xrQ3vUP2HG5JBB1iZnVSsbBXPcn6M1aL9I= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=google.com; spf=pass smtp.mailfrom=google.com; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b=Kk5GTAF8; arc=none smtp.client-ip=209.85.214.176 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.b="Kk5GTAF8" Received: by mail-pl1-f176.google.com with SMTP id d9443c01a7336-2b2e8b95bdbso2485ad.0 for ; Mon, 18 May 2026 07:01:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20251104; t=1779112898; x=1779717698; darn=vger.kernel.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=J/DDwNmydnZ95awbzSL1/xD68dz5V6Sw49Abl3+3NpU=; b=Kk5GTAF8yZbICqo34orGOy7kAHN/xjMcb6DHedlQsj3x1cofzUCsDLw318LfVZWlNN 0jdbMplSr59a21y0H+Xp/l/A5q7Ecj6QR5rpUw3RlZ7W8qq8hT0UUlo8P6UatE/cTLXD F+09V2EiXFiEN7EeppU5C06mHn9pmazd2mr9Q29itqEu72QdMt6beugOPYPZ8k65dNqD U0OpQ82RZWeJTSfwIm7suEqZY0ODtpaiPPS/dlBKnVmNgb4xdKJDmmDGexkZ9ru0mqL3 P5auiMXerMLsE6TXd83qHzjVYfSKUArsWDvYlzG1I9F+j2LoRrjyW6f8hIeaf3UPB/wM mC8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1779112898; x=1779717698; h=in-reply-to:content-disposition: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; bh=J/DDwNmydnZ95awbzSL1/xD68dz5V6Sw49Abl3+3NpU=; b=mADkvzaK0ITVBCUPlck6H8T2m1Mso2CKgc1xfurdPRj0Jyhc6QZ1XKnhhL2SM6FTZ9 kIkkllUbUGsBgbaaDB/QAh6ZT+/V1RiawtJTa6O+dxjCbEiRMZBC/aZvftrHjSyYg4JG JsMCvE8s+AqUdW3dy7bzZF/OJhtRhd4xfS6eJXgEROeLanLWOBr6PzeANUf20vf3fobA nZNVH92cIt/oTD7cK9Q+DO2xwH7ddjnU0XZZf2aZ/RCJZS7SJqJ+nTJovsJf8xv4yDIJ atatMmJmKkcWfZJlrioz8yluJ7rKzIhVY0ufmeKE6jF3SQokuIRVc9v2t+Hq4yc6v3Ls FLjA== X-Forwarded-Encrypted: i=1; AFNElJ/LUvQI1w17ZFxTOkoxbC+anf0ISI0B+efUWucvPUJICLYdzA1YHNZLMR5O2HICVPnqPT+3v1ZEPrscmVA=@vger.kernel.org X-Gm-Message-State: AOJu0YwKzWLPjtV/QmJ2Q6z0UlIENIBfXjHVUc4LwTuohgvIHPpl8sPY ILf/qvS2rrbn4LMxAuS5IVz5IpTb+fDMkAot+yfNbgnzJ8eEY6zRZxCKBCvmXYia+w== X-Gm-Gg: Acq92OETQRlqmfNamCeb1bc8JvRmREXy6wquJ0yKjQC8s9+IweJKoYsyvmv1YQ70YFe B8Z+GQQ7B6WkSi4D4no7mXQlmO6h/8mM8f8eH8kgjEGXNG6yUbGS52wYJ1i6HiJkAgLMCFATcFj i11MEglsFPB594h0TagtljRUg/5diFkiLtHUAFP7KHXEEjYhz+FXJSPRcCyFEgni3z61IBjD6dT uIU5xUowUIZywaHRNnZ3DblabGgarWaUaqT+GCWkpcNaZWfcvCfqyHVFC1imBq8p0vrMMRyy1OE zyIjOhpSk9lO5zJ9NtY785eJYer+1iKJ4VGgq+tfpt8tibKGAgnDEU0gTOvkUp9hraiT4tM8qGT RB2fEbAMsXq3itiOUkKxgM4aMsgQpAeZQw6BQuK6sX91Aq6Lwc66OdbjKhShLEOGQm+Sj0PR0dT zId2yMs9GkHiic2NKa9WoVGZKYnwvLNdqNQQ7wdUhwOfav9/X01sE/zSeaa/jghJrhnHjq X-Received: by 2002:a17:903:fa6:b0:2bd:a61:8536 with SMTP id d9443c01a7336-2bdb03a448amr2847385ad.6.1779112895495; Mon, 18 May 2026 07:01:35 -0700 (PDT) Received: from google.com (44.234.124.34.bc.googleusercontent.com. [34.124.234.44]) by smtp.gmail.com with ESMTPSA id d9443c01a7336-2bd5d11b495sm159037515ad.69.2026.05.18.07.01.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 18 May 2026 07:01:34 -0700 (PDT) Date: Mon, 18 May 2026 14:01:25 +0000 From: Pranjal Shrivastava To: Samiullah Khawaja Cc: Baolu Lu , David Woodhouse , Joerg Roedel , Will Deacon , Jason Gunthorpe , Robin Murphy , Kevin Tian , Alex Williamson , Shuah Khan , iommu@lists.linux.dev, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, Saeed Mahameed , Adithya Jayachandran , Parav Pandit , Leon Romanovsky , William Tu , Pratyush Yadav , Pasha Tatashin , David Matlack , Andrew Morton , Chris Li , Vipin Sharma , YiFei Zhu Subject: Re: [PATCH v2 04/16] iommu: Implement device and IOMMU HW preservation Message-ID: References: <20260427175633.1978233-1-skhawaja@google.com> <20260427175633.1978233-5-skhawaja@google.com> <3874a086-98ae-4b94-8c1b-20e13f5a92fb@linux.intel.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Thu, May 07, 2026 at 06:47:07PM +0000, Samiullah Khawaja wrote: > On Thu, May 07, 2026 at 10:07:43AM +0800, Baolu Lu wrote: > > On 4/28/26 01:56, Samiullah Khawaja wrote: > > > Add IOMMU ops to preserve/unpreserve a device. These can be implemented > > > by the IOMMU drivers that support preservation of devices that have > > > their IOMMU domains preserved. During device preservation the state of > > > the associated IOMMU is also preserved as dependency. > > > > > > Signed-off-by: Samiullah Khawaja > > > --- > > > drivers/iommu/liveupdate.c | 162 +++++++++++++++++++++++++++++++ > > > include/linux/iommu-liveupdate.h | 33 +++++++ > > > include/linux/iommu.h | 20 ++++ > > > 3 files changed, 215 insertions(+) > > > > > [snip] > > > + > > > +int iommu_preserve_device(struct iommu_domain *domain, > > > + struct device *dev, u64 *preserved_state) > > > +{ > > > + struct iommu_flb_obj *flb_obj; > > > + struct iommu_device_ser *device_ser; > > > + struct dev_iommu *iommu; > > > + struct pci_dev *pdev; > > > + int ret; > > > + > > > + if (!dev_is_pci(dev)) > > > + return -EOPNOTSUPP; > > > + > > > + if (!domain->preserved_state) > > > + return -EINVAL; > > > + > > > + if (!iommu_group_dma_owner_claimed(dev->iommu_group)) > > > + return -EINVAL; > > > + > > > + pdev = to_pci_dev(dev); > > > + iommu = dev->iommu; > > > + if (!iommu->iommu_dev->ops->preserve_device || > > > + !iommu->iommu_dev->ops->preserve) > > > + return -EOPNOTSUPP; > > I will check for unpreserve ops here also. [snip] > > > + pdev = to_pci_dev(dev); > > > + iommu = dev->iommu; > > > + if (!iommu->iommu_dev->ops->unpreserve_device || > > > + !iommu->iommu_dev->ops->unpreserve) > > > + return; > > > > Is it considered a driver bug if it implements the preserve hooks but > > not unpreserve ones? This would at least cause a silent memory leak. How > > about adding a WARN like this? > > I think the preservation should not be done if the unpreserve ops are > not implemented by the driver. I will add these checks in the _preserve > functions and return EOPNOTSUPP if it is not implemented by the driver. > > > > if (WARN_ON_ONCE(!iommu->iommu_dev->ops->unpreserve_device || > > !iommu->iommu_dev->ops->unpreserve)) > > return; > > We can add this warning here also. I'd rather have the iommu device registration fail instead of solely relying on these WARN_ONs here. We can simply add a snippet inside iommu_device_register(): #ifdef CONFIG_IOMMU_LIVEUPDATE if ((iommu->ops->preserve && !iommu->ops->unpreserve) || (!iommu->ops->preserve && iommu->ops->unpreserve)) { pr_err("IOMMU: %s: Asymmetric live-update operations detected\n", dev_name(iommu->dev)); return -EINVAL; } #endif This prevents a half-baked iommu driver from ever spinning up, completely eliminating the need to check for it inside the live-update session paths. We anyway don't support hot-pluggable liveupdate ops atm. Thanks, Praan