- 03 Dec, 2010 8 commits
-
-
Ben Skeggs authored
Signed-off-by:Ben Skeggs <bskeggs@redhat.com>
-
Francisco Jerez authored
nouveau_channel_ref() takes a "weak" channel reference that doesn't prevent the hardware channel resources from being released, it just keeps the channel data structure alive. Signed-off-by:
Francisco Jerez <currojerez@riseup.net> Signed-off-by:
-
Francisco Jerez authored
Signed-off-by:
-
Francisco Jerez authored
The destroy_context() engine hooks call gpuobj management functions to release the channel resources, these functions use HARDIRQ-unsafe locks whereas destroy_context() is called with the HARDIRQ-safe context_switch_lock held, that's a lock ordering violation. Push the engine-specific channel destruction logic into destroy_context() and let the hardware-specific code lock and unlock when it's actually needed. Change the engine destruction order to avoid a race in the small gap between pgraph and pfifo context uninitialization. Reported-by:
Marcin Slusarz <marcin.slusarz@gmail.com> Signed-off-by:
-
Ben Skeggs authored
Not used at all yet, but lets hook it up now anyway. Signed-off-by: -
Ben Skeggs authored
No other driver uses this, and userspace should be responsible for handling locking between them if they share BOs. Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
This fixes a race condition between fbcon acceleration and TTM buffer moves. To reproduce: - start X - switch to vt and "while (true); do dmesg; done" - switch to another vt and "sleep 2 && cat /path/to/debugfs/dri/0/evict_vram" - switch back to vt running dmesg We don't make use of this on any other channel yet, they're currently protected by drm_global_mutex. This will change in the near future. Signed-off-by:
-
- 18 Nov, 2010 4 commits
-
-
Andy Lutomirski authored
The old code generated an interrupt storm bad enough to completely take down my system. Signed-off-by:
Andy Lutomirski <luto@mit.edu> Signed-off-by:
-
Ben Skeggs authored
Signed-off-by: -
Francisco Jerez authored
This will be needed for Z compression and to take smarter placement decisions. Signed-off-by:
-
Francisco Jerez authored
Remove some unused/duplicated definitions and make sparse happy again. Signed-off-by:
-
- 04 Oct, 2010 8 commits
-
-
Francisco Jerez authored
Reported-by:
Christoph Bumiller <e0425955@student.tuwien.ac.at> Signed-off-by:
Maarten Maathuis <madman2003@gmail.com> Tested-by:
Xavier Chantry <chantry.xavier@gmail.com> Tested-by:
-
Francisco Jerez authored
Signed-off-by:
-
Francisco Jerez authored
Signed-off-by:
-
Francisco Jerez authored
Mainly to make room for inter-channel sync. Signed-off-by:
-
Marcin Kościelnicki authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
On certain boards, there's BIOS scripts and memory timings that need to be modified with the memclk. Just pass in the entire perflvl struct and let the chipset-specific code decide what to do. Signed-off-by: -
Roy Spliet authored
This isn't correct everywhere yet, but since we don't use the data yet it's perfectly safe to push in, and the information we gain from logs will help to fix the remaining issues. v2 (Ben Skeggs <bskeggs@redhat.com>): - fixed up formatting - free parsed timing info on takedown - switched timing table printout to debug loglevel Signed-off-by:
Roy Spliet <r.spliet@student.tudelft.nl> Signed-off-by:
-
- 24 Sep, 2010 20 commits
-
-
Francisco Jerez authored
Signed-off-by:
-
Martin Peres authored
Signed-off-by:
Martin Peres <martin.peres@ensi-bourges.fr> Signed-off-by:
-
Ben Skeggs authored
Guarded by a module parameter for the moment, read the code for the magic value which enables it. Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
This replaces all the pll_types definitions for ones that match the types used in the tables in recent VBIOS versions. get_pll_limits() will now accept either type or register value as input across all limits table versions, and will store the actual register ID that a PLL type refers to in the returned structure. Signed-off-by: -
Francisco Jerez authored
Instead of emptying the caches to avoid a race with the PFIFO puller, go straight ahead and try to recover from it when it happens. Also, kill pfifo->cache_flush and tile->lock, we don't need them anymore. Signed-off-by:
-
Francisco Jerez authored
Signed-off-by:
-
Francisco Jerez authored
Signed-off-by:
-
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Reviewed-by:
-
Ben Skeggs authored
Reviewed-by:
-
Ben Skeggs authored
Reviewed-by:
-
Ben Skeggs authored
Reviewed-by:
-
Ben Skeggs authored
Reviewed-by:
-
Ben Skeggs authored
Will be used at a later point when we plug in an alternative VRAM memory manager for GeForce 8+ boards. Based on pscnv code to do the same. Signed-off-by:
Marcin Kościelnicki <koriakin@0x04.net> Signed-off-by:
-
Ben Skeggs authored
Reviewed-by:
-
Ben Skeggs authored
Reviewed-by:
-
Ben Skeggs authored
Reviewed-by:
-
Ben Skeggs authored
Reviewed-by:
-
Ben Skeggs authored
Reviewed-by:
-
