[PATCH libdrm] amdgpu: fix "add AMDGPU_VA_RANGE_HIGH"
Christian König
ckoenig.leichtzumerken at gmail.com
Wed Feb 28 15:25:40 UTC 2018
Am 28.02.2018 um 16:21 schrieb Michel Dänzer:
> On 2018-02-28 03:41 PM, Christian König wrote:
>> The 32bit address range end is exclusive, not inclusive.
> The other way around. :) Inclusive means [a,b], i.e. an interval
> including the endpoints, whereas exclusive means ]a,b[, i.e. an interval
> not including the endpoints. The patch changes the 32-bit address range
> endpoint from exclusive to inclusive.
Actually that's not what I meant. How about this:
"The range is stored as exclusive, not inclusive. Subtracts one to get
the inclusive interval for the calculation."
>> This fixes crashes when 32bit addresses are in use.
>>
>> Signed-off-by: Christian König <christian.koenig at amd.com>
> With the above fixed,
>
> Reviewed-and-Tested-by: Michel Dänzer <michel.daenzer at amd.com>
>
>
More information about the amd-gfx
mailing list