<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Apr 26, 2017 at 1:20 AM, Juan A. Suarez Romero <span dir="ltr"><<a href="mailto:jasuarez@igalia.com" target="_blank">jasuarez@igalia.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Tue, 2017-04-25 at 23:42 -0700, Jason Ekstrand wrote:<br>
> On Mon, Apr 24, 2017 at 5:17 PM, Andres Gomez <<a href="mailto:agomez@igalia.com">agomez@igalia.com</a>> wrote:<br>
> > Hi Jason,<br>
> ><br>
> > this patch landed in master with Cc to stable.<br>
> ><br>
> > However, the changes need commit 656e30b6860 and quite some other<br>
> > dependencies (util/build_id.h)<br>
> ><br>
> > Additionally, Tapani is mentioning problems in Android and the<br>
> > probability of the issue that is trying to fix seems unlikely (?).<br>
> ><br>
> > Should we drop this patch from the stable branch?<br>
><br>
> We probably can but I'd mildly prefer not. I'm not sure what issue Tapani is hitting but I suspect it's just android not setting the right --build-id flag.<br>
> <br>
<br>
<br>
</span>Just to make it clear, we are talking about dropping it for 17.0.4, but<br>
keep for 17.1.<br>
<br>
Unfortunately, for 17.0.4 it would require several other commits that<br>
are not in the 17.0 branch.<br>
<br>
Another alternative would be submitting a specific patch for 17.0 that<br>
does the same, but do not rely on those commits.<br></blockquote><div><br></div><div>I think dropping it is fine for now. We can come up with something if we actually ever see the bug in the wild<br><br></div><div>--Jason<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
> > Br.<br>
> ><br>
> > On Thu, 2017-04-20 at 10:11 +0300, Tapani Pälli wrote:<br>
> > ><br>
> > > On 03/14/2017 04:26 AM, Jason Ekstrand wrote:<br>
> > > > This prevents a user from using a cache created on one hardware<br>
> > > > generation on a different one. Of course, with Intel hardware, this<br>
> > > > requires moving their drive from one machine to another but it's still<br>
> > > > possible and we should prevent it.<br>
> > > ><br>
> > > > Reviewed-by: Chad Versace <<a href="mailto:chadversary@chromium.org">chadversary@chromium.org</a>><br>
> > > > ---<br>
> > > > src/intel/vulkan/anv_device.c | 22 +++++++++++++++++-----<br>
> > > > 1 file changed, 17 insertions(+), 5 deletions(-)<br>
> > > ><br>
> > > > diff --git a/src/intel/vulkan/anv_device.<wbr>c b/src/intel/vulkan/anv_device.<wbr>c<br>
> > > > index be2b2f3..5db0a6c 100644<br>
> > > > --- a/src/intel/vulkan/anv_device.<wbr>c<br>
> > > > +++ b/src/intel/vulkan/anv_device.<wbr>c<br>
> > > > @@ -32,6 +32,7 @@<br>
> > > > #include "util/strtod.h"<br>
> > > > #include "util/debug.h"<br>
> > > > #include "util/build_id.h"<br>
> > > > +#include "util/mesa-sha1.h"<br>
> > > > #include "util/vk_util.h"<br>
> > > ><br>
> > > > #include "genxml/gen7_pack.h"<br>
> > > > @@ -53,17 +54,28 @@ compiler_perf_log(void *data, const char *fmt, ...)<br>
> > > > }<br>
> > > ><br>
> > > > static bool<br>
> > > > -anv_device_get_cache_uuid(<wbr>void *uuid)<br>
> > > > +anv_device_get_cache_uuid(<wbr>void *uuid, uint16_t pci_id)<br>
> > > > {<br>
> > > > const struct build_id_note *note = build_id_find_nhdr("libvulkan_<wbr>intel.so");<br>
> > > > if (!note)<br>
> > > > return false;<br>
> > > ><br>
> > > > - unsigned len = build_id_length(note);<br>
> > > > - if (len < VK_UUID_SIZE)<br>
> > > > + unsigned build_id_len = build_id_length(note);<br>
> > > > + if (build_id_len < 20) /* It should be a SHA-1 */<br>
> > ><br>
> > > This line here causes issues for Android, for us the build_id_len seems<br>
> > > to be 16 (and worked before nicely as check was against VK_UUID_SIZE<br>
> > > which is 16). I just bisected this and haven't yet figured out why but<br>
> > > will check.<br>
> > ><br>
> > > // Tapani<br>
> > > ______________________________<wbr>_________________<br>
> > > mesa-dev mailing list<br>
> > > <a href="mailto:mesa-dev@lists.freedesktop.org">mesa-dev@lists.freedesktop.org</a><br>
> > > <a href="https://lists.freedesktop.org/mailman/listinfo/mesa-dev" rel="noreferrer" target="_blank">https://lists.freedesktop.org/<wbr>mailman/listinfo/mesa-dev</a><br>
> > --<br>
> > Br,<br>
> ><br>
> > Andres<br>
> ><br>
><br>
</div></div>> ______________________________<wbr>_________________<br>
> mesa-stable mailing list<br>
> <a href="mailto:mesa-stable@lists.freedesktop.org">mesa-stable@lists.freedesktop.<wbr>org</a><br>
> <a href="https://lists.freedesktop.org/mailman/listinfo/mesa-stable" rel="noreferrer" target="_blank">https://lists.freedesktop.org/<wbr>mailman/listinfo/mesa-stable</a><br>
</blockquote></div><br></div></div>