Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp2765119imj; Mon, 11 Feb 2019 08:08:33 -0800 (PST) X-Google-Smtp-Source: AHgI3IblbxjJNQFnu2++G5xjLC1LqJ0QgguZgDRpWpgru8nzvgTxYTaRLeKUg5FmkPSNlf2xB+ie X-Received: by 2002:a63:d450:: with SMTP id i16mr33740341pgj.246.1549901312968; Mon, 11 Feb 2019 08:08:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549901312; cv=none; d=google.com; s=arc-20160816; b=Tl42jVpYpjXfr+TXbMoFhpfwQg7ycLfZxq+pKMEoH+/FtHhTIFHBV1/u2KxzUA4QMz BdehfH3wZzVfHrT4zq4AxC0yx6mS119lG/s9V93wm7pTLeriAw67mkC8rW+XAMyJeM0F s9cFABM96l6+DOMC4R5f/aOM6jsTI95smYFuelj1U4Yrgxc0rpHkKwgWsYzj3DDoIMq3 vkDXlf+Wd5I2UkHXWkUhWs8RM/lPxJ0jh4wVUawH1mQ6qDb6de9wpwrGCVDjfbaNQHSU pPckXhushE5CPRQBmqcyz4WDFnZAMr20GRzvLv+RIPYN4EGLFBapG1I9K424k/ii2+6T ZcYA== 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=FfzRbFbQIl2GLYDLRZwOW85EBgeicsIPNbblKB+kQkA=; b=GYak9mBaxEDzeiy20HYG865EP91KuM0trEeiUoihf2I5doSlGyLtUQBkSeYsN3GUbj Xwl/weaCZLkIdcRYYLoPBo0B5AQhwuBXZPEXw6WsN4rgetlTrsQgGBNRLFmnPL4iivws 1dJD92hPt9gWHw9y0cg/iKUFSGs0rrQBsllhUrlaf8+AD4sIVhiLtW19UKYID7ufaFuz 62ou9Kb/5qN6apvXWsMCOybtt2A+rNgB1AUkzXlKjVSEnaTL5Na7/IVoEg0FBsxRBAse fRN6CqthJrtoLJFUgnJQzBMIcYJdIA6HIpuEOwDbW2oSZruVzgBf61o+hoLH2YkIVVjO cmog== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=ThAWxSjW; 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 d15si9279900pgv.583.2019.02.11.08.08.12; Mon, 11 Feb 2019 08:08:32 -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=ThAWxSjW; 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 S1729628AbfBKO0x (ORCPT + 99 others); Mon, 11 Feb 2019 09:26:53 -0500 Received: from mail.kernel.org ([198.145.29.99]:60780 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729608AbfBKO0w (ORCPT ); Mon, 11 Feb 2019 09:26:52 -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 563F92075C; Mon, 11 Feb 2019 14:26:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1549895211; bh=1SdnDbIotud4h1uvDmQrJkx7PigJD95SbH2SP2QCJjs=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=ThAWxSjWLWi6YNJJyN4N5h1dqMMMxTW89+aSfSD248OXfWMDyDBttiRxQfEcP5u7V mVdGrtG+YhNgtuMZrVaBUUZkOKGBmwEyqzIhB8SSqC/ME7ARgzOiLNJgXztbm64ZWW GdIBPgQBkNbEDq6eu0GlhUYG0hHSKV1nq7BnmIk8= 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.20 130/352] iommu/amd: Fix amd_iommu=force_isolation Date: Mon, 11 Feb 2019 15:15:57 +0100 Message-Id: <20190211141854.703324382@linuxfoundation.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190211141846.543045703@linuxfoundation.org> References: <20190211141846.543045703@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.20-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 1167ff0416cf..325f3bad118b 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