[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] seccomp raises on mesa pthread_setaffinity_np()

From: Daniel P . Berrangé
Subject: Re: [Qemu-devel] seccomp raises on mesa pthread_setaffinity_np()
Date: Wed, 27 Feb 2019 11:45:34 +0000
User-agent: Mutt/1.10.1 (2018-07-13)

On Fri, Feb 22, 2019 at 09:04:53AM +0100, Marc-André Lureau wrote:
> Hi,
> We have another seccomp issue with mesa, leading to SIGSYS bad system
> call (when running a virgl VM with libvirt for example)

To close the circle, this is now also reported on launchpad


> Since commit :
> https://gitlab.freedesktop.org/mesa/mesa/commit/d877451b48a59ab0f9a4210fc736f51da5851c9a
> (unfortunately, already in f29)
> mesa wants to set its thread affinity on all CPU, but I am not sure
> how we can limit the rule to the mesa threads yet... any ideas?

Per my comment on the bug, I think this is not a good default behaviour
for Mesa. It should honour the affinity of the process that is running,
because if that has been given restrictive CPU affinity it is precisely
because the admin or mgmt app doesn't want it to use all CPUs. Mesa
shouldn't unconditionally undo that decision.

> Another reason to consider vhost-user-gpu, to simplify the seccomp rules!

I don't think that's going to help because if anything I expect seccomp
rules to be more restrictive for the vhost processes as they are tailored
to specific functional niches. Even if in a separate process libvirt will
still not want mesa to violate the CPU affinity it has configured. It must
honour what the process was given.

|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

reply via email to

[Prev in Thread] Current Thread [Next in Thread]