From: "Christian König" <christian.koenig@amd.com>
To: Christoph Hellwig <hch@lst.de>, Gabriel C <nix.or.die@gmail.com>
Cc: "Tom Lendacky" <thomas.lendacky@amd.com>,
"Jean-Marc Valin" <jmvalin@mozilla.com>,
"Dave Airlie" <airlied@linux.ie>,
"Felix Kuehling" <Felix.Kuehling@amd.com>,
LKML <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org,
"Christian König" <christian.koenig@amd.com>,
"Joerg Roedel" <jroedel@suse.de>,
alexander.deucher@amd.com,
"Andrew Morton" <akpm@linux-foundation.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Michel Dänzer" <michel@daenzer.net>
Subject: Re: Kernel and ADM hardware roulette ( was AMD graphics performance regression in 4.15 and later )
Date: Fri, 8 Jun 2018 08:52:52 +0200 [thread overview]
Message-ID: <1c8b3938-6656-5d5a-f65d-dfd2e55d989e@amd.com> (raw)
In-Reply-To: <20180608060223.GB24107@lst.de>
Am 08.06.2018 um 08:02 schrieb Christoph Hellwig:
> On Thu, Jun 07, 2018 at 02:32:46PM +0200, Gabriel C wrote:
>> Ok done.. bisect points to:
> What is the failure mode you are seeing? Can't find anything in the
> mail unfortunately.
As far as I analyzed it we now get an -ENOMEM from dma_alloc_attrs() in
drivers/gpu/drm/ttm/ttm_page_alloc_dma.c when IOMMU is enabled.
Still need to figure out which parameters we want to use for the
allocation, but I think it is only 4k or 8k.
Regards,
Christian.
next prev parent reply other threads:[~2018-06-08 6:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 13:33 Gabriel C
2018-06-06 14:12 ` Michel Dänzer
2018-06-06 14:44 ` Christian König
2018-06-06 15:03 ` Michel Dänzer
2018-06-06 15:44 ` Gabriel C
2018-06-07 7:07 ` Christian König
2018-06-07 12:32 ` Gabriel C
2018-06-07 16:24 ` Gabriel C
2018-06-07 17:20 ` Christian König
2018-06-08 6:01 ` Christoph Hellwig
2018-06-08 6:47 ` Christian König
2018-06-08 6:02 ` Christoph Hellwig
2018-06-08 6:52 ` Christian König [this message]
2018-06-08 13:32 ` Gabriel C
2018-06-11 7:15 ` Christoph Hellwig
2018-06-11 19:23 ` Linus Torvalds
2018-06-06 15:24 ` Gabriel C
2018-06-06 14:29 ` Christian König
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=1c8b3938-6656-5d5a-f65d-dfd2e55d989e@amd.com \
--to=christian.koenig@amd.com \
--cc=Felix.Kuehling@amd.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=alexander.deucher@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@lst.de \
--cc=jmvalin@mozilla.com \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@daenzer.net \
--cc=nix.or.die@gmail.com \
--cc=thomas.lendacky@amd.com \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®