<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - qemu using spice gl and sandbox resourcecontrol=deny crashes with SIGSYS on radeonsi" href="https://bugs.freedesktop.org/show_bug.cgi?id=109695#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - qemu using spice gl and sandbox resourcecontrol=deny crashes with SIGSYS on radeonsi" href="https://bugs.freedesktop.org/show_bug.cgi?id=109695">bug 109695</a> from <a class="email" href="mailto:dan-freedesktop@berrange.com" title="Daniel P. Berrange <dan-freedesktop@berrange.com>"> Daniel P. Berrange</a> <pre>(In reply to Ahzo from <a href="show_bug.cgi?id=109695#c0">comment #0</a>) > The problematic code at src/util/u_queue.c:252 was added in the following > commit: > commit d877451b48a59ab0f9a4210fc736f51da5851c9a > Author: Marek Olšák <<a href="mailto:marek.olsak@amd.com">marek.olsak@amd.com</a>> > Date: Mon Oct 1 15:51:06 2018 -0400 > > util/u_queue: add UTIL_QUEUE_INIT_SET_FULL_THREAD_AFFINITY > > Initial version discussed with Rob Clark under a different patch name. > This approach leaves his driver unaffected. > > > Since setting the thread affinity seems non-essential here, the failing > syscall should be handled gracefully, for example by setting a signal > handler to ignore the SIGSYS signal. I'm curious what motivated this change to start with ? Even if QEMU was not enforcing seccomp filters, I think I'd consider it a bug for mesa to be setting its process affinity in this way. The mgmt application or sysadmin has decided that the process must have a certain affinity, based on how it/they want the host CPUs utilized. Why is mesa wanting to override this administrative policy decision to restrict CPU usage ?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>