Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp2667618imj; Mon, 11 Feb 2019 06:44:51 -0800 (PST) X-Google-Smtp-Source: AHgI3IYSIb46YFVNp7+TbtjicLydo6iVfyi0mOY7FviIgRyNDCj2aHVoUA2xGQzjL2vnjy+5vK8G X-Received: by 2002:a63:d709:: with SMTP id d9mr25731166pgg.157.1549896291398; Mon, 11 Feb 2019 06:44:51 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549896291; cv=none; d=google.com; s=arc-20160816; b=QR3/xPRTfuy2SJEEt15GFTQtmma0+WUT/9mbagyuWl6XJBFLw9UEaU3+cQ82vqjp+v 8GmCBZYIuyPl1I2OXUqk1Cg3CgzEdKoo/lxcCp6qoegKKMvNaYVtut3bxe8u0oaBcF5t wy1+nHO8QEopRGsRaAYdKA06EoC8s8YRSHq8yXgVYUnLUxNBtl8w5L0Pk3RZx/4GXLSf cugMjsev87XnM6Bx4L9/iKZR2lXCx9iTc3MOs0JqWymaYiH9UhTpck5Hbt4TWH6ck0Tx EEBw+TyuzgqRn2yPPe6FGwPvDIrZ96c/XWbS6fWWtYhAP8IPR0BW0hfopb1WnbkBuYDO pc1A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=Xs0aoWYS0gLa+bc0jLsflwNk1/gHNtd8xs3AEvtxD28=; b=mmOGD+ywuF6adjlCqLsrbxYAXJVTQVeVGKvJxFA7dwebto+P4+sBXvoEazozNr0etP rYQ0OaOorggXHaDr3+ARDiQTeSQG0KdyGluJ8WtXVH6ICwXvUfiVtQKLeU2f9dfm7W3b eMX205oDu8OCnn329e8LNmTrDMX6mIT0iCdNzk8jqScW/Y/fZ1oZGWzPrkeD8rRuZAv1 TYK5+z6h+IDtUxOE2O/wP0p736eODqcfr/xQErSHXMXTRh15m+yZPlmfwEHlFynh7Zqj IyBdQhvXjxZRB/y5q11KsSIu4FftIQzr/vOJ0TrJXjaOvgUZhaOBo29xQt9ZSagYBuSv JCDQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="GrukTKI/"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a31si8382041pgl.376.2019.02.11.06.44.35; Mon, 11 Feb 2019 06:44:51 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="GrukTKI/"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732684AbfBKOnm (ORCPT + 99 others); Mon, 11 Feb 2019 09:43:42 -0500 Received: from mail.kernel.org ([198.145.29.99]:55900 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732673AbfBKOni (ORCPT ); Mon, 11 Feb 2019 09:43:38 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 8D064222A2; Mon, 11 Feb 2019 14:43:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1549896218; bh=hoMUS8kZf5JkUNDg/gt7cFKkdZHHCc9RtMINp3quCl8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=GrukTKI/33PUYHwSMPVfVFqNKfPJoiEdYeT0WAXpC+KnjRKq5YwoUeBe8oKFATGA6 +82Fj6pFCSAZnVYQnPI/gmZO6OrcQ87zu5tzuhsY5xBf2mv4v3LR0D/FzpjYpUuKdf U5HSmPbbgWK17j/FQe7nMXHUVvU2r0CC3twEz5xw= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Yu Zhao , Joerg Roedel , Sasha Levin Subject: [PATCH 4.19 111/313] iommu/amd: Fix amd_iommu=force_isolation Date: Mon, 11 Feb 2019 15:16:31 +0100 Message-Id: <20190211141901.285423872@linuxfoundation.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190211141852.749630980@linuxfoundation.org> References: <20190211141852.749630980@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review X-Patchwork-Hint: ignore MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.19-stable review patch. If anyone has any objections, please let me know. ------------------ [ Upstream commit c12b08ebbe16f0d3a96a116d86709b04c1ee8e74 ] The parameter is still there but it's ignored. We need to check its value before deciding to go into passthrough mode for AMD IOMMU v2 capable device. We occasionally use this parameter to force v2 capable device into translation mode to debug memory corruption that we suspect is caused by DMA writes. To address the following comment from Joerg Roedel on the first version, v2 capability of device is completely ignored. > This breaks the iommu_v2 use-case, as it needs a direct mapping for the > devices that support it. And from Documentation/admin-guide/kernel-parameters.txt: This option does not override iommu=pt Fixes: aafd8ba0ca74 ("iommu/amd: Implement add_device and remove_device") Signed-off-by: Yu Zhao Signed-off-by: Joerg Roedel Signed-off-by: Sasha Levin --- drivers/iommu/amd_iommu.c | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c index bee0dfb7b93b..34c9aa76a7bd 100644 --- a/drivers/iommu/amd_iommu.c +++ b/drivers/iommu/amd_iommu.c @@ -438,7 +438,14 @@ static int iommu_init_device(struct device *dev) dev_data->alias = get_alias(dev); - if (dev_is_pci(dev) && pci_iommuv2_capable(to_pci_dev(dev))) { + /* + * By default we use passthrough mode for IOMMUv2 capable device. + * But if amd_iommu=force_isolation is set (e.g. to debug DMA to + * invalid address), we ignore the capability for the device so + * it'll be forced to go into translation mode. + */ + if ((iommu_pass_through || !amd_iommu_force_isolation) && + dev_is_pci(dev) && pci_iommuv2_capable(to_pci_dev(dev))) { struct amd_iommu *iommu; iommu = amd_iommu_rlookup_table[dev_data->devid]; -- 2.19.1