<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - R9270X pyrit benchmark perf regressions with latest kernel/llvm"
href="https://bugs.freedesktop.org/show_bug.cgi?id=82050#c25">Comment # 25</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - R9270X pyrit benchmark perf regressions with latest kernel/llvm"
href="https://bugs.freedesktop.org/show_bug.cgi?id=82050">bug 82050</a>
from <span class="vcard"><a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> <span class="fn">Michel Dänzer</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=82050#c24">comment #24</a>)
<span class="quote">> Just a general note: We need to define that flag negated for compatibility
> reasons. E.g. RADEON_GEM_NO_CPU_ACCESS because code must assume with an old
> client that the buffer is always CPU accessed.</span >
No, CPU access works fine even with old clients which don't set the flag.
The flag is just an optimization, preventing BOs which are expected to be
accessed by the CPU from being stored in the CPU-inaccessible part of VRAM.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>