From: Jean-Marc Valin <jmvalin@mozilla.com>
To: christian.koenig@amd.com, airlied@linux.ie,
alexander.deucher@amd.com, Felix.Kuehling@amd.com,
labbott@redhat.com, akpm@linux-foundation.org,
michel.daenzer@amd.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: AMD graphics performance regression in 4.15 and later
Date: Mon, 9 Apr 2018 11:17:43 -0400 [thread overview]
Message-ID: <76a30815-28e3-e798-03de-a3cdfade4c64@mozilla.com> (raw)
In-Reply-To: <55e1712b-6567-50c5-3789-53dd1ccddb94@gmail.com>
On 04/09/2018 05:42 AM, Christian König wrote:
> Backporting all the detection logic is to invasive, but you could just
> go into drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c and forcefull use the
> other code path.
>
> Just look out for "#ifdef CONFIG_SWIOTLB" checks and disable those.
Do you mean just taking the 4.15 code as is and replacing
"#ifdef CONFIG_SWIOTLB" with "#if 0" in
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c or are you talking about using a
different version of drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c ?
Jean-Marc
next prev parent reply other threads:[~2018-04-09 15:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 0:30 Jean-Marc Valin
2018-04-06 8:03 ` Christian König
2018-04-06 8:10 ` Christian König
2018-04-06 15:30 ` Jean-Marc Valin
2018-04-09 11:48 ` Christian König
2018-04-06 16:42 ` Jean-Marc Valin
2018-04-06 17:20 ` Christian König
2018-04-06 22:00 ` Jean-Marc Valin
2018-04-09 9:42 ` Christian König
2018-04-09 15:17 ` Jean-Marc Valin [this message]
2018-04-10 6:48 ` Christian König
2018-04-11 4:00 ` Gabriel C
2018-04-11 5:02 ` Gabriel C
2018-06-06 11:28 ` Gabriel C
2018-06-06 11:33 ` Christian König
2018-06-06 12:08 ` Gabriel C
2018-06-06 12:19 ` Christian König
2018-04-11 9:37 ` Christian König
2018-04-11 14:26 ` Gabriel C
2018-04-11 17:21 ` Gabriel C
2018-04-11 18:35 ` Jean-Marc Valin
2018-04-11 22:20 ` Gabriel C
2018-04-12 1:47 ` Gabriel C
2018-04-20 14:47 ` Michel Dänzer
2018-04-20 19:40 ` Felix Kuehling
2018-04-23 10:23 ` Michel Dänzer
2018-07-13 2:23 ` Jean-Marc Valin
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=76a30815-28e3-e798-03de-a3cdfade4c64@mozilla.com \
--to=jmvalin@mozilla.com \
--cc=Felix.Kuehling@amd.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michel.daenzer@amd.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome