diff options
author | Chris Wilson <[email protected]> | 2015-07-21 11:12:57 +0100 |
---|---|---|
committer | Chris Wilson <[email protected]> | 2015-07-24 17:38:55 +0100 |
commit | 013d731a67538a2eb8f508fa54bb86191f0e5491 (patch) | |
tree | 7d3e7d58c4c307354a151c34180a2bc02fb28f92 /src/mesa/main/queryobj.h | |
parent | 30f97b5e52b324d501c56df8902d294fb755a5b7 (diff) |
i965: Use updated kernel interface for accurate TIMESTAMP reads
I was mistaken, I thought we already had fixed this in the kernel a
couple of years ago. We had not, and the broken read (the hardware
shifts the register output on 64bit kernels, but not on 32bit kernels) is
now enshrined into the ABI. I also had the buggy architecture reversed,
believing it to be 32bit that had the shifted results. On the basis of
those mistakes, I wrote
commit c8d3ebaffc0d7d915c1c19d54dba61fd1e57b338
Author: Chris Wilson <[email protected]>
Date: Wed Apr 29 13:32:38 2015 +0100
i965: Query whether we have kernel support for the TIMESTAMP register once
Now that we do have an extended register read interface for always
reporting the full 36bit TIMESTAMP (irrespective of whether the hardware
is buggy or not), make use of it and in the process fix my reversed
detection of the buggy reads for unpatched kernels.
Signed-off-by: Chris Wilson <[email protected]>
Cc: Martin Peres <[email protected]>
Cc: Kenneth Graunke <[email protected]>
Cc: MichaĆ Winiarski <[email protected]>
Cc: Daniel Vetter <[email protected]>
Tested-and-acked-by: Chris Forbes <[email protected]>
Reviewed-by: Daniel Vetter <[email protected]>
Diffstat (limited to 'src/mesa/main/queryobj.h')
0 files changed, 0 insertions, 0 deletions