- Jan 28, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Start to print detailed Vulkan info for every GPU See merge request !226
-
Ludovico de Nittis authored
Provide /etc/amd, /var/tmp, /run/host/etc, /run/gfx/etc in container See merge request !232
-
Ludovico de Nittis authored
Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
Ludovico de Nittis authored
Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
Ludovico de Nittis authored
Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
Ludovico de Nittis authored
This helps us to avoid leaking variables. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
Ludovico de Nittis authored
Now that check-vulkan prints detailed information about every physical and virtual Vulkan GPU, we can start to provide this info in s-r-s-i too. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Jan 27, 2021
-
-
Simon McVittie authored
We share /tmp with the host, and it seems odd to share /tmp but put /var/tmp on our private tmpfs, particularly when /var/tmp is traditionally longer-lived and more spacious than /tmp (for example, /tmp on a small tmpfs and /var/tmp on a large disk is common). In the unusual case where we are using a fake $HOME, we mount its ~/.cache/tmp on our container's /var/tmp, consistent with Flatpak. That doesn't change here, and it's still persistent unless explicitly deleted. Prompted by <https://github.com/ValveSoftware/steam-runtime/issues/313#issuecomment-766526963 > Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Normally it does, so applications might misbehave if they can't create files and directories inside it without needing to create it first. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
The root filesystem of the container is a tmpfs anyway, so we don't need a separate tmpfs. This is consistent with what Flatpak does. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
We could make a symlink /etc/amd -> /run/host/etc/amd or /run/gfx/etc/amd, as appropriate, but this seems neater. Resolves: https://github.com/ValveSoftware/steam-runtime/issues/313 Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
We'll use this in more places in a subsequent commit. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
We take the same action for each of these files, so let's make the code more data-driven. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Similar to the previous commit, if the graphics stack provider is not the host, we want to put its /etc in /run/gfx/etc, alongside /run/gfx/usr. Partially addresses <https://github.com/ValveSoftware/steam-runtime/issues/313 >. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
There are three user-space Vulkan driver stacks for recent AMD GPUs: - Mesa RADV, open-source drivers from the Mesa community - AMDVLK, open-source drivers from AMD - AMDGPU-PRO, proprietary drivers from AMD (presumably based on AMDVLK) At least one of the two AMD-maintained drivers requires files that are installed in /etc/amd. Partially addresses <https://github.com/ValveSoftware/steam-runtime/issues/313 >. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Ludovico de Nittis authored
system-info: Record more environment variables See merge request !231
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Inspired by <https://github.com/ValveSoftware/steam-runtime/issues/357 > which turned out to be a distro patch from a version of Slackware that didn't support PulseAudio, forcing SDL to use ALSA even though the user had upgraded to a version of Slackware that *does* support PulseAudio. Various environment variables set by the Steam package on Flathub are also included. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
If one of the variables we are interested in happens to be set already, and doesn't get overridden, then the test will fail. For example, `DRI_PRIME=1 meson test -C _build` would fail. This will become a lot more likely to happen when I start logging ubiquitous environment variables like `DISPLAY`. We can't just set envp = NULL initially, because g_environ_setenv() in Ubuntu 12.04 won't accept NULL as a valid environment block (although newer versions do). Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Ludovico de Nittis authored
With the commit 0d0b054a we redirected the JSON results to stderr as a stopgap solution. Now we revert that and print the results in stdout so that we can implement a proper parsing. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Jan 26, 2021
-
-
Simon McVittie authored
check-vulkan: Fix compilation on Steam Runtime 1½ 'heavy' See merge request !230
-
Simon McVittie authored
heavy is still on Vulkan loader v1.1.73, which doesn't know VK_ERROR_INVALID_DRM_FORMAT_MODIFIER_PLANE_LAYOUT_EXT. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
check-vulkan: Temporarily print JSON details of GPUs to stderr See merge request !229
-
Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
Simon McVittie authored
When the corresponding code in SrtGraphics is ready, we can parse the JSON on stdout and produce machine-readable output from steam-runtime-system-info. However, until we have that, human-readable output is better than nothing. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jan 25, 2021
-
-
Ludovico de Nittis authored
Represent diagnostic messages as arrays See merge request !227
-
Simon McVittie authored
Various improvements to check-vulkan See merge request !222
-
Simon McVittie authored
A single line with escaped newlines is unnecessarily hard to read. This repurposes code that we already had for printing a udev uevent pseudo-file in this way. We retain the ability to parse old s-r-s-i output in which the diagnostic messages were a string: the intended meaning is fairly obvious. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
The reference is now the man page. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Ludovico de Nittis authored
system-info: Log more influential environment variables See merge request !223
-
Ludovico de Nittis authored
When we call the check-vulkan helper we will have in output information about all the available physical GPUs and also a separate JSON object that tells us if the GPU 0 is able to draw the triangle test. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Jan 21, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Backport the new json_from_string() function See merge request !224
-
Ludovico de Nittis authored
JSON-GLib 1.2.0 introduced a new function called `json_from_string()`. It is an handy function that allows us to obtain a jsonNode with just a single operation. This function had to be backported, and modified a little, because we are targeting Scout that has an older JSON-GLib version that misses both `json_from_string()` and `json_parser_steal_root()` (that was used in `json_from_string()`). Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
Ludovico de Nittis authored
Without this knowledge, `_srt_find_myself()` will fail to return the right prefix for statically-linked installed tests. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-