From: "Michel Dänzer" <michel@daenzer.net>
To: Oded Gabbay <oded.gabbay@amd.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: Regression caused by "drm/radeon: Don't increment pipe_id in kgd_init_pipeline"
Date: Tue, 17 Feb 2015 13:03:25 +0900 [thread overview]
Message-ID: <54E2BD8D.4010906@daenzer.net> (raw)
In-Reply-To: <54E1D43B.3030903@amd.com>
On 16.02.2015 20:27, Oded Gabbay wrote:
>
>
> On 02/13/2015 12:01 PM, Michel Dänzer wrote:
>>
>> Hi Oded,
>>
>>
>> the commit in the subject (5a8888a3119eb5b67f6e90605be9ed2e04807126)
>> somehow causes degraded CPU (!) performance on my Kaveri box. E.g. a
>> piglit run takes about 15% longer, and I suspect the same is true for
>> e.g. compiling the kernel, though I haven't measured that explicitly.
>>
>> In addition to the measurably worse performance, the commit causes the
>> CPU fan to stay significantly quieter during CPU-bound tasks, so maybe
>> the commit somehow causes the CPU not to achieve turbo clocks or
>> something like that.
>>
>> I'm attaching my .config. I don't see any difference in dmesg with or
>> without the commit.
>>
>>
> Hi Michel,
> Thanks for catching that.
> As we talked on IRC, there is indeed a bug in amdkfd.
> I will publish the fix you tested to be included in 3.20 and mark it as
> stable.
> I will also add piglit to my regression tests.
Sounds good, thanks!
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2015-02-17 4:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 10:01 Regression caused by "drm/radeon: Don't increment pipe_id in kgd_init_pipeline" Michel Dänzer
2015-02-16 11:27 ` Oded Gabbay
2015-02-17 4:03 ` Michel Dänzer [this message]
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=54E2BD8D.4010906@daenzer.net \
--to=michel@daenzer.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=oded.gabbay@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