New issue
Advanced search Search tips

Issue 892678 link

Starred by 4 users
Status: Assigned
Owner:
ddavenp...@chromium.org
Cc:
dgreid@chromium.org
za...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

grunt: restore crosvm-wl-dmabuf USE flag

Project Member Reported by ddavenp...@chromium.org, Oct 5 
The flag was removed in https://chromium-review.googlesource.com/c/chromiumos/overlays/board-overlays/+/1257650

From the CL description:
"The multiprocess mode of crosvm does not work when it uses minigbm on
radeonsi cards (such as on grunt), which spawns a background thread. The
background thread trips a protective assert when crosvm forks device
processes which behave badly when in multithreaded processes."

Comment 1 by ddavenp...@chromium.org, Oct 6 

It might be worth experimenting with setting the environment variable GALLIUM_THREAD=0. It looks like this might avoid creating the extra thread, though it's not clear what the performance penalty might be. Maybe better than disabling virtwl-dmabuf altogether?

https://gitlab.freedesktop.org/mesa/mesa/blob/master/src/gallium/auxiliary/util/u_threaded_context.c#L2565

https://lists.freedesktop.org/archives/mesa-dev/2017-May/155162.html

Comment 2 by djkurtz@google.com, Jan 9

Components: OS>Kernel>Graphics OS>Systems>Containers
Labels: -Pri-3 M-74 Pri-2
Owner: ddavenp...@chromium.org
Status: Assigned (was: Untriaged)
Assigning over to ddavenport to investigate a bit further and route as needed.
►

Sign in to add a comment