<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [SKL][v4.3 bisected]SKL OpenCL performance reduced hugely"
href="https://bugs.freedesktop.org/show_bug.cgi?id=92975#c14">Comment # 14</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [SKL][v4.3 bisected]SKL OpenCL performance reduced hugely"
href="https://bugs.freedesktop.org/show_bug.cgi?id=92975">bug 92975</a>
from <span class="vcard"><a class="email" href="mailto:currojerez@riseup.net" title="Francisco Jerez <currojerez@riseup.net>"> <span class="fn">Francisco Jerez</span></a>
</span></b>
<pre>(In reply to rongyang from <a href="show_bug.cgi?id=92975#c12">comment #12</a>)
<span class="quote">> Thanks for your patch.
> But how could beignet got the MOCS values exposed by the kernel, if kernel
> will change these values in the future, how could beignet get the needed one?</span >
The meaning of the MOCS entries already exposed by the kernel shouldn't ever
change in a non-backwards-compatible way, only new entries will be added at the
end of the table. The exposed MOCS entries are considered part of the kernel
ABI so in principle you can rely on them staying the same in future kernel
versions.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>