Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp1753277imu; Sat, 10 Nov 2018 00:39:58 -0800 (PST) X-Google-Smtp-Source: AJdET5eiD21dw/4DoadgTVnnQEQu5nD2e0NXb4ih+rvsY8zPgBpKsK+HaCkSoxjgShdzyxyYDfZG X-Received: by 2002:a62:6981:: with SMTP id e123-v6mr12160247pfc.104.1541839198146; Sat, 10 Nov 2018 00:39:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541839198; cv=none; d=google.com; s=arc-20160816; b=MNJ0gNzhsN1TdVzXumpar8BHkRysgqQi4HDVImRntsXBqDY0UoORV5kpAJGVmJkYWN H0oTg3ofRLN5BASwcDyX9NpM74rqpv+GKw1I397sEfsVh6F9gLfO+PBmHCs05DQKsUA6 KHOTF0NCGNmrBecOamhKPFR/I+Hax8vEQXK7nMsDXYSL8so6FNQDxufdv/BjuJeghAlk EkWUSx89pbLdJTd7eUw6NlajrgQLZ221+WMLwkFEnraVOwhyav52LvxrBlfnmz0GI/C6 /pTCC76ogzweCGbhpwoZhuSXhN0aSXgFkrhRlbPdwd5gKVpsIN7yDyO250uwKgPLfrtc NK4Q== 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 :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=LTXVECQRBmDhZRZneSXyNQhQ5ls4nzApasQhZXfypRk=; b=FkmbWKdRXZAlxYiA8aD4MUEf2ImjvxtUixCD7ipXQBcMS2OBVIyAtVDZP26PMPyosE nYT5ACSjN/d1/nttUs//TRLYiUe/anjzaLAngBV6HGHMl3HqcZ4wbtgFB1e/H/Fq6vfu OqWgMZQNbcA5aXXTAoQWaEcWjQJ4ixRYmKNXyTqdy69RLj7mp5IUIWPtg2kUIXoRimeu FhfxdIhJ8kUxHrr4OAw7w3f10ut304TxRFn21bjmJLug82PCM4na4/GeI66zR3j6t4iD D/HwyJfHnWwlLPYnmrp7DVWLJw8JtZCbYhKvlBO8xvKiGZGPhbS7aQ+75L7Np5vM/XGb uYZg== ARC-Authentication-Results: i=1; mx.google.com; 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 u5-v6si615618plj.295.2018.11.10.00.39.42; Sat, 10 Nov 2018 00:39:58 -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; 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 S1728916AbeKJSXd (ORCPT + 99 others); Sat, 10 Nov 2018 13:23:33 -0500 Received: from mx2.suse.de ([195.135.220.15]:44324 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726272AbeKJSXc (ORCPT ); Sat, 10 Nov 2018 13:23:32 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 92B2DADAB; Sat, 10 Nov 2018 08:39:20 +0000 (UTC) Date: Sat, 10 Nov 2018 09:39:18 +0100 From: Jean Delvare To: David Airlie Cc: christian.koenig@amd.com, "Iwai, Takashi" , dri-devel , linux-kernel Subject: Re: Performance regression in ast drm driver Message-ID: <20181110093918.52ec9f0f@endymion> In-Reply-To: References: <20181101162707.598c1718@endymion> <20181108130509.3b2d42ff@endymion> Organization: SUSE Linux X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.31; x86_64-suse-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 9 Nov 2018 10:04:03 +1000, David Airlie wrote: > This seems likely to be a hw problem with PCI writes to the AST "GPU", > since it's just some sort of RAM + ARM on the end of a PCIE bus, we've > definitely seen possible issues in the past with write combining > around some of the mga GPUs with some CPUs. > > Have we seen the problem across a number of AST devices? The reports I received from customers were all on AST 2500 devices (on Supermicro X11DPi-N, Supermicro X11DPH-T and Asus WS C621 Sage). I was able to reproduce "the problem" on my old Asus Z6NA-D6 which has either an AST 2050 device if I trust the board specifications on asus.com, or an AST 1100 if I trust /var/log/Xorg.0.log. Note however that I am still not certain that the problem I am seeing is the same as what both customers reported. It is possible that we have 2 different issues. -- Jean Delvare SUSE L3 Support