From: Harry Wentland <harry.wentland-5C7GfCeVMHo@public.gmane.org>
To: "Christian König"
<deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>,
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Cc: "Alex Deucher" <Alexander.Deucher-5C7GfCeVMHo@public.gmane.org>,
"Tony Cheng" <Tony.Cheng-5C7GfCeVMHo@public.gmane.org>,
"Dmytro Laktyushkin"
<Dmytro.Laktyushkin-5C7GfCeVMHo@public.gmane.org>,
"Michel Dänzer" <michel.daenzer-5C7GfCeVMHo@public.gmane.org>,
"Christian König" <christian.koenig-5C7GfCeVMHo@public.gmane.org>
Subject: Re: [PATCH] drm/amd/display: Limit DCN to x86 arch
Date: Fri, 19 May 2017 15:36:39 -0400 [thread overview]
Message-ID: <7a8b84af-38f7-33d2-5bbb-473f2ea35bb2@amd.com> (raw)
In-Reply-To: <f84c51b6-06f1-b4d2-c472-89265ebb26cb-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
On 2017-05-19 11:02 AM, Christian König wrote:
> Am 19.05.2017 um 16:01 schrieb Harry Wentland:
>> DCN bw calcs currently rely on the following gcc options:
>> -mhard-float -msse -mpreferred-stack-boundary=4
>
> Mhm, price question: Why does DCN rely on the gcc options?
>
Tony and Dmytro can probably provide more info here but my understanding
is that DCN bandwidth calcs requires floating point support. This code
comes pretty much straight from hardware teams with a guarantee that the
output is good.
If we were to rewrite bandwidth calculations that guarantee would
basically fly out the window, which means when there's a bandwidth bug
we cannot easily get HW support unless we can prove that our
calculations yield the exact same results in all cases as HWs formula.
Covering all scenarios that bandwidth calcs covers would be quite an
extensive undertaking and I'm sure we'd miss important cases.
Bandwidth issues can be very hard to pin down and changes in the
calculations can have significant impact on our power efficiency.
> That is something very unusual for drivers. We occasionally have
> something like enabling additional warnings, but things like
> "-mhard-float" is clearly raising an eyebrow here.
>
Absolutely, and I'd love to hear more opinions on this.
Harry
> Christian.
>
>>
>> We probably shouldn't allow building this on architectures
>> other than x86.
>>
>> CC: Alex Deucher <Alexander.Deucher@amd.com>
>> CC: Christian König <christian.koenig@amd.com>
>> CC: Michel Dänzer <michel.daenzer@amd.com>
>> CC: Tony Cheng <Tony.Cheng@amd.com>
>> CC: Dmytro Laktyushkin <Dmytro.Laktyushkin@amd.com>
>> Signed-off-by: Harry Wentland <harry.wentland@amd.com>
>> ---
>>
>> Tested this change by running make menuconfig and make modules with
>> ARCH=arm.
>>
>> Harry
>>
>> drivers/gpu/drm/amd/display/Kconfig | 2 +-
>> drivers/gpu/drm/amd/display/dc/calcs/Makefile | 2 ++
>> 2 files changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/amd/display/Kconfig
>> b/drivers/gpu/drm/amd/display/Kconfig
>> index 2b8d77cebe03..62ea9f600374 100644
>> --- a/drivers/gpu/drm/amd/display/Kconfig
>> +++ b/drivers/gpu/drm/amd/display/Kconfig
>> @@ -11,7 +11,7 @@ config DRM_AMD_DC
>> config DRM_AMD_DC_DCN1_0
>> bool "DCN 1.0 Raven family"
>> - depends on DRM_AMD_DC
>> + depends on DRM_AMD_DC && X86
>> help
>> Choose this option if you want to have
>> RV family for display engine
>> diff --git a/drivers/gpu/drm/amd/display/dc/calcs/Makefile
>> b/drivers/gpu/drm/amd/display/dc/calcs/Makefile
>> index a095472bf4b5..2e4ce0918c02 100644
>> --- a/drivers/gpu/drm/amd/display/dc/calcs/Makefile
>> +++ b/drivers/gpu/drm/amd/display/dc/calcs/Makefile
>> @@ -3,9 +3,11 @@
>> # It calculates Bandwidth and Watermarks values for HW programming
>> #
>> +ifeq ($(ARCH),x86)
>> CFLAGS_dcn_calcs.o := -mhard-float -msse -mpreferred-stack-boundary=4
>> CFLAGS_dcn_calc_auto.o := -mhard-float -msse
>> -mpreferred-stack-boundary=4
>> CFLAGS_dcn_calc_math.o := -mhard-float -msse
>> -mpreferred-stack-boundary=4
>> +endif
>> BW_CALCS = dce_calcs.o bw_fixed.o custom_float.o
>
>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2017-05-19 19:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 14:01 [PATCH] drm/amd/display: Limit DCN to x86 arch Harry Wentland
[not found] ` <20170519140121.14296-1-harry.wentland-5C7GfCeVMHo@public.gmane.org>
2017-05-19 14:54 ` Lazare, Jordan
2017-05-19 15:02 ` Christian König
[not found] ` <f84c51b6-06f1-b4d2-c472-89265ebb26cb-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2017-05-19 19:36 ` Harry Wentland [this message]
[not found] ` <7a8b84af-38f7-33d2-5bbb-473f2ea35bb2-5C7GfCeVMHo@public.gmane.org>
2017-05-19 20:18 ` Dave Airlie
[not found] ` <CAPM=9tzcA8t-ji6qNQhycB0cezz2vH6HMixCgvKQ78cY1Y8fsA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-19 20:28 ` Harry Wentland
[not found] ` <4e0c342b-d18e-5f7a-bd30-9becd0e97e3c-5C7GfCeVMHo@public.gmane.org>
2017-05-20 8:13 ` Christian König
[not found] ` <013f44e3-1734-43f8-4cd7-e950ffb014f0-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2017-05-23 13:37 ` Harry Wentland
[not found] ` <ff8918ec-ee0e-692e-4ada-cd6bd939d902-5C7GfCeVMHo@public.gmane.org>
2017-05-23 14:57 ` Felix Kuehling
2017-05-24 1:09 ` 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=7a8b84af-38f7-33d2-5bbb-473f2ea35bb2@amd.com \
--to=harry.wentland-5c7gfcevmho@public.gmane.org \
--cc=Alexander.Deucher-5C7GfCeVMHo@public.gmane.org \
--cc=Dmytro.Laktyushkin-5C7GfCeVMHo@public.gmane.org \
--cc=Tony.Cheng-5C7GfCeVMHo@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=christian.koenig-5C7GfCeVMHo@public.gmane.org \
--cc=deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org \
--cc=michel.daenzer-5C7GfCeVMHo@public.gmane.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 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.