From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1030573AbdDZVby (ORCPT <rfc822;w@1wt.eu>);
        Wed, 26 Apr 2017 17:31:54 -0400
Received: from smtp-out-so.shaw.ca ([64.59.136.138]:34466 "EHLO
        smtp-out-so.shaw.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S967769AbdDZVbq (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 26 Apr 2017 17:31:46 -0400
X-Authority-Analysis: v=2.2 cv=UpATD64B c=1 sm=1 tr=0
 a=JyAt4amVi6RK7kaaDbhaBA==:117 a=JyAt4amVi6RK7kaaDbhaBA==:17
 a=IkcTkHD0fZMA:10 a=AzvcPWV-tVgA:10 a=MWpn0KmTea4u40F2yvIA:9 a=QEXdDO2ut3YA:10
Subject: Re: AMD IOMMU causing filesystem corruption
To: Joerg Roedel <joro@8bytes.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
References: <5ea65f55-e5eb-11a5-14ab-e721d2f95ed6@sieb.net>
 <20170403213909.GR7266@8bytes.org>
 <32afc9d1-a2db-f9dc-bbe0-d894967dc8ad@sieb.net>
 <935473d9-e75b-c019-0dde-063855067858@sieb.net>
 <20170404073215.GS7266@8bytes.org>
 <5838b65d-0f2f-86b1-1041-a28d42fc9881@sieb.net>
 <20170407102739.GY7266@8bytes.org>
 <4e1ccc54-440b-b848-5623-2c5849e2d0c1@sieb.net>
 <20170426101405.GJ7266@8bytes.org>
From: Samuel Sieb <samuel@sieb.net>
Message-ID: <c6d33a95-1bfe-1c33-e0ed-95060ab7fcc7@sieb.net>
Date: Wed, 26 Apr 2017 14:31:40 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <20170426101405.GJ7266@8bytes.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-CA
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfKhqX0IW24lHw+sHgRz4v22xlrHEMKdkGjrpTtDpY27DgPKI7smjbLBUC+VBZaHPWJXHVg1VNYaSSbERpisnmNok/zimQytw8ja4x1dpoovWhCtn+u5A
 rU2LI1Ep3BR7eHrimVAJAHmh0uk9LeYLvB/wciWzs66hE5gEJBZQvY5qVFa3ZUq7wglznI4qAHI8lmim2XSQTsrf6pD7ervJVcg=
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 04/26/2017 03:14 AM, Joerg Roedel wrote:
> On Tue, Apr 25, 2017 at 10:55:24AM -0700, Samuel Sieb wrote:
>> On 04/07/2017 03:27 AM, Joerg Roedel wrote:
>>> Also, please try the attached debug-diff on your kernel. It completly
>>> disables the use of ATS in the amd-iommu driver.
>>>
>> I applied this patch to 4.11.0 rc8 and then stress tested the laptop
>> with another kernel build while running graphical applications and
>> there appears to be no damage to the filesystem.  Is there any way
>> to determine if ATS is enabled or disabled?
> 
> Great, thanks for testing the patch. The lspci tool should be able to
> tell you whether the ATS capability is enabled on the GPU. With a
> 'lspci -vvv -s <GPUDEV>" should give you that info.
> 
This test was done with the patch that always disables ATS.  Which is 
the current patch to selectively disable it?  The last patch I tried 
didn't seem to work.