From: Jean Delvare <jdelvare@suse.de>
To: David Airlie <airlied@redhat.com>
Cc: christian.koenig@amd.com, "Iwai, Takashi" <tiwai@suse.de>,
dri-devel <dri-devel@lists.freedesktop.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Performance regression in ast drm driver
Date: Sat, 10 Nov 2018 09:39:18 +0100 [thread overview]
Message-ID: <20181110093918.52ec9f0f@endymion> (raw)
In-Reply-To: <CAMwc25oWstf8bFfWfb=FFR8GfFhx+jM77TzqE-qfi+ev2pMvFw@mail.gmail.com>
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
next prev parent reply other threads:[~2018-11-10 8:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 15:27 Performance regression in ast drm driver Jean Delvare
2018-11-08 12:05 ` Jean Delvare
2018-11-09 0:04 ` David Airlie
2018-11-10 8:39 ` Jean Delvare [this message]
2018-11-12 14:36 ` Jean Delvare
2018-11-12 14:45 ` Takashi Iwai
2018-11-12 16:41 ` Jean Delvare
2018-11-13 9:23 ` Thomas Zimmermann
2018-11-13 9:23 ` Thomas Zimmermann
2018-11-13 12:08 ` Jean Delvare
2018-11-13 12:16 ` Thomas Zimmermann
2018-11-13 12:16 ` Thomas Zimmermann
2018-11-12 19:36 ` Thomas Zimmermann
2018-11-13 8:19 ` YC Chen
2018-11-13 8:19 ` YC Chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181110093918.52ec9f0f@endymion \
--to=jdelvare@suse.de \
--cc=airlied@redhat.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.