From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: "Michel Dänzer" <michel@daenzer.net>,
"Tom St Denis" <tom.stdenis@amd.com>
Cc: Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
Christian Zigotzky <chzigotzky@xenosoft.de>
Subject: Re: Hardware 3D acceleration doesn't work anymore with the latest git kernel
Date: Mon, 27 Nov 2017 12:50:59 +0100 [thread overview]
Message-ID: <d6b1857f-70da-8ff9-bc59-1e31c64622d9@gmail.com> (raw)
In-Reply-To: <d1dc6a21-e85e-96cf-5878-ce294c33b54a@daenzer.net>
Hi Michel,
Am 27.11.2017 um 12:02 schrieb Michel Dänzer:
> Hi Tom,
>
> On 2017-11-24 05:09 PM, Michel Dänzer wrote:
>> On 2017-11-24 03:29 PM, Christian Zigotzky wrote:
>>> Hi All,
>>>
>>> I bisected today and the first bad commit is:
>>> a4dec819c8bba6365eb893a4ca88db4dd1210110 (drm/ttm: Add helper functions
>>> to populate/map in one call (v2)) [1]
>> It can't really be that commit, since it just adds functions but doesn't
>> hook them up anywhere. Presumably it's commit
>> f7871fd19389c5f64f625a4389675d0740f0dfe4 ("drm/radeon: use new TTM
>> populate/dma map helper functions") instead, which makes the radeon
>> driver rely on ttm_populate_and_map_pages, which is just a stub
>> returning -ENOMEM when neither CONFIG_SWIOTLB nor CONFIG_INTEL_IOMMU is
>> enabled.
>>
>> I can see two possible solutions:
>>
>> 1. Make ttm_populate_and_map_pages and ttm_unmap_and_unpopulate_pages
>> work without SWIOTLB / INTEL_IOMMU as well.
>>
>> 2. Make the drivers work without ttm_populate_and_map_pages and
>> ttm_unmap_and_unpopulate_pages again in that case.
>>
>>
>> Solution 1 would be preferable.
> Which solution do you want to go for?
well, can somebody please explain to me why those patches actually
result in problems?
They should have only moved code around, not cause anything like this.
Apart from that I also prefer solution 1.
Regards,
Christian.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-11-27 11:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 18:08 Hardware 3D acceleration doesn't work anymore with the latest git kernel Christian Zigotzky
2017-11-21 4:38 ` Alex Deucher
2017-11-21 11:32 ` Christian Zigotzky
2017-11-22 13:20 ` Christian Zigotzky
2017-11-22 13:27 ` Ilia Mirkin
2017-11-22 13:40 ` Christian Zigotzky
2017-11-22 13:45 ` Ilia Mirkin
2017-11-22 14:53 ` Christian Zigotzky
2017-11-24 14:29 ` Christian Zigotzky
2017-11-24 16:09 ` Michel Dänzer
2017-11-24 19:08 ` Christian Zigotzky
2017-11-24 19:13 ` Christian Zigotzky
2017-11-24 19:14 ` Ilia Mirkin
2017-11-24 20:58 ` Christian Zigotzky
2017-11-27 11:02 ` Michel Dänzer
2017-11-27 11:50 ` Christian König [this message]
2017-11-27 12:02 ` Michel Dänzer
2017-11-27 12:17 ` Tom St Denis
2017-11-27 14:53 ` Michel Dänzer
2017-11-28 5:43 ` Christian Zigotzky
2017-11-28 9:40 ` Michel Dänzer
2017-11-28 23:48 ` Christian Zigotzky
2017-11-27 12:20 ` Christian König
2017-11-29 8:50 ` Michel Dänzer
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=d6b1857f-70da-8ff9-bc59-1e31c64622d9@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=christian.koenig@amd.com \
--cc=chzigotzky@xenosoft.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=michel@daenzer.net \
--cc=tom.stdenis@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;
as well as URLs for NNTP newsgroup(s).