| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| | |
ssh://cgit.freedesktop.org/~tball/mesa-gallium-vdpau into pipe-video
|
| |\ |
|
|\ \ \
| |/ /
|/| /
| |/ |
ssh://cgit.freedesktop.org/~tball/mesa-gallium-vdpau into pipe-video
|
| |
| |
| |
| |
| |
| |
| | |
Since flush rework there could be only one relocation per
register in a block.
Signed-off-by: Jerome Glisse <[email protected]>
|
| |
| |
| |
| | |
Got a speed up by tracking the dirty blocks in a seperate list instead of looping through all blocks. This version should work with block that get their dirty state disabled again and I added a dirty check during the flush as some blocks were already dirty.
|
| |
| |
| |
| | |
Also fix link to release notes in 7.9-rc1 news item.
|
| |
| |
| |
| | |
Partially cherry-picked from commit 61653b488da76ee1ca4f77363e222d3b717dd865
|
| |
| |
| |
| | |
(cherry picked from commit c19bc5de961fe5e1f8a17131bcfae3dbcccaca29)
|
| |
| |
| |
| | |
(cherry picked from commit 41e371e351cc4c77b2b20a545af2dfa2dab253d7)
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Flush read cache before writting register. Track flushing inside
of a same cs and avoid reflushing same bo if not necessary. Allmost
properly force flush if bo rendered too and then use as a texture
in same cs (missing pipeline flush dunno if it's needed or not).
Signed-off-by: Jerome Glisse <[email protected]>
|
| |
| |
| |
| |
| |
| |
| | |
Allow fast lookup of relocation information & id which
was a CPU time consumming operation.
Signed-off-by: Jerome Glisse <[email protected]>
|
| | |
|
| | |
|
|\|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
configs/linux-dri
configure.ac
src/gallium/drivers/nvfx/Makefile
src/gallium/include/pipe/p_defines.h
src/gallium/include/pipe/p_screen.h
src/gallium/include/state_tracker/dri1_api.h
src/gallium/include/state_tracker/drm_api.h
src/gallium/tests/python/samples/tri.py
src/gallium/tests/trivial/Makefile
src/gallium/tests/unit/Makefile
src/gallium/tests/unit/SConscript
src/gallium/tests/unit/u_format_test.c
src/gallium/winsys/nouveau/drm/nouveau_drm_api.c
|
| |
| |
| |
| | |
we weren't decreasing when removing from the list.
|
| |
| |
| |
| |
| |
| | |
if we know the bo has gone not busy, no need to add another bo wait
thanks to Andre (taiu) on irc for pointing this out.
|
| |
| |
| |
| | |
since we plan on using dx10 constant buffers everywhere.
|
| |
| |
| |
| | |
we don't use this since constant buffers are now being used on all gpus.
|
| |
| |
| |
| |
| |
| | |
When we go to do a lot of bos in one draw like constant bufs we need
to avoid bouncing off the busy ioctl, this mitigates by backing off
on busy bos for a short amount of times.
|
| |
| |
| |
| |
| | |
If we assume busy buffers are added to the list in order its unlikely
we'd fine one after the first busy one that isn't busy.
|
| |
| |
| |
| |
| | |
this just keeps a list of bos submitted together, and uses them to decide
bo busy state for the whole group.
|
| |
| |
| |
| | |
NOTE: this is a candidate for the 7.9 branch.
|
| |
| |
| |
| |
| |
| | |
These texture formats (like R16G16B16A16_UNORM) were untested until now
because st/mesa doesn't use them. I am testing this with a hacked st/mesa
here.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I am trying to be exhaustive, but still I might have missed tons of other
changes to Gallium.
(cherry picked from commit 968a9ec76eadf55e8b58171884e1175d7b8cf59a)
Conflicts:
docs/relnotes-7.9.html
|
| | |
|
| |
| |
| |
| |
| | |
This uses message headers for now, since we'll need it for MRT. We
can cut out the header later.
|
| |
| |
| |
| | |
It instead sensibly appears in the src0 slot.
|
| |
| |
| |
| |
| |
| | |
We could try to detect this in expression handling and do it
proactively there, but it seems like less logic to do it in one
optional pass at the end.
|
| |
| |
| |
| |
| |
| |
| | |
The glsl core should be handling most dead code issues for us, but we
generate some things in codegen that may not get used, like the 1/w
value or pixel deltas. It seems a lot easier this way than trying to
work out up front whether we're going to use those values or not.
|
| |
| |
| |
| | |
This also means that our intervals now highlight dead code.
|
| | |
|
| |
| |
| |
| | |
Signed-off-by: Jerome Glisse <[email protected]>
|
| |
| |
| |
| | |
Signed-off-by: Jerome Glisse <[email protected]>
|
| |
| |
| |
| | |
Signed-off-by: Jerome Glisse <[email protected]>
|
| |
| |
| |
| |
| |
| |
| | |
Add bo offset everywhere needed if r600_bo is ever a sub bo
of a bigger bo.
Signed-off-by: Jerome Glisse <[email protected]>
|
| |
| |
| |
| | |
Signed-off-by: Jerome Glisse <[email protected]>
|
| |
| |
| |
| | |
From AROS.
|
| |
| |
| |
| |
| | |
no wonder it was slow, the code is deliberately forcing stuff into GTT,
we used to have domain management but it seems to have disappeared.
|