search for: ttms

Am 09.01.24 um 09:14 schrieb Thomas Hellstr?m: > Hi, Christian > > On Tue, 2024-01-09 at 08:47 +0100, Christian K?nig wrote: >> Hi guys, >> >> I'm trying to make this functionality a bit more useful for years now >> since we multiple reports that behavior of drivers can be suboptimal >> when multiple placements be given. >> >> So basically

On 9 July 2014 22:29, Maarten Lankhorst <maarten.lankhorst at canonical.com> wrote: > Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com> > --- > drivers/gpu/drm/radeon/radeon.h | 15 +- > drivers/gpu/drm/radeon/radeon_device.c | 60 ++++++++- > drivers/gpu/drm/radeon/radeon_fence.c | 223 ++++++++++++++++++++++++++------ > 3 files

...----- Welcome to Knowledge Vision! Our systems and programs can help you to successfully optimize your professional potential in a changing world. To be able to progress efficiently in any area today, we promote new smart working and learning systems through new techniques, tools and methodologies (TTMs) in key Smart Learning Areas: Knowledge Management, Change Management, Quantitative Learning, Qualitative Learning, Skill Management and Business Intelligence. For more information visit our web www.amjsmartlearning.com info@amjsmartlearning.com ----------------------------- If you would like to u...

...r driver you can just ignore that part and do process based waits everywhere. > >I'm sure you have some ideas and I think you really need to > >investigate them to move this thing forward, > >even it if means some issues with android sync pts. > > Actually I think that TTMs fence interface already gave quite a good hint > how it might look like. I can only guess that this won't fit with the > Android stuff, otherwise I can't see a good reason why we didn't stick with > that. Well the current plan for i915<->radeon sync from Maarten is to us...

...ginning. Good to know that I'm not the only one thinking that this isn't such a good idea. > I'm sure you have some ideas and I think you really need to > investigate them to move this thing forward, > even it if means some issues with android sync pts. Actually I think that TTMs fence interface already gave quite a good hint how it might look like. I can only guess that this won't fit with the Android stuff, otherwise I can't see a good reason why we didn't stick with that. > but none of the two major drivers seem to want the interface as-is so > some...

...e CPU to the GPU and vice-versa. Thanks to the feedback received on the previous revisions I believe this code looks rather good now. I also have extensively tested it and could not see any buffer corruption issue anymore. There is still one point which is not completely satisfying in my opinion: TTMs for TTM-backed objects are allocated in nouveau_sgdma_create_ttm() and populated in nouveau_ttm_tt_populate(). Coherently-allocated buffers need to use the ttm_dma API instead of the pool-based TTM API, and whether an object is coherent or not is stored in its instance of nouveau_bo. The problem i...