- Oct 24, 2023
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This is necessary for a full replacement for _srt_file_test_in_sysroot(). Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Just for consistency: we know that self->provider->in_current_ns is fdio-based. 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
This is only for consistency, and no functional change is intended: we know that the interpreter root is constructed as a fdio-based object. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
We need to be a bit careful here, because we can only interpret dynamic string tokens like `${LIB}` if we're using the real root, which we previously represented as path `/` but now represent with `_srt_sysroot_new_direct()`. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Ludovico de Nittis authored
graphics-drivers: Resolve files in a sysroot more correctly See merge request !602
-
Ludovico de Nittis authored
pv-runtime: Use a SrtSysroot to represent the real root See merge request !617
-
Ludovico de Nittis authored
graphics: Write out exactly the original content of Vulkan/EGL driver manifests See merge request !614
-
Ludovico de Nittis authored
system-info: Add path/version of s-r-s-i as the first things in the report See merge request !594
-
Simon McVittie authored
This will let us tell at a glance which version of the diagnostic tool a given report came from. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
If it isn't a directory, then it can't possibly contain files. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
We will want this later, to be able to pass it to interfaces that have been converted to take a SrtSysroot. No functional change. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Otherwise we will miss FEX-Emu's path rewriting. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
These can't possibly contain VDPAU modules. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This ensures that FEX-Emu's path rewriting is still effective. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This avoids being tricked by absolute symlinks in a non-trivial sysroot. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This avoids reading the wrong location if absolute symlinks are involved, while still allowing FEX-Emu to rewrite paths when not acting on a sysroot. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This avoids escaping from the sysroot if there is an absolute symlink, while still letting FEX-Emu rewrite paths while not acting on a sysroot. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This avoids some overly long lines, and repetition of the code to prepend layers to the list. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This avoids repetition of the common code to construct a SrtVulkanLayer object in error state and prepend it to the list. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This prevents symlinks from inadvertently "escaping" from the sysroot, while also doing the right thing to take into account FEX-Emu's pseudo-overlayfs. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This swaps PvRuntime from using `/` to `/proc/self/root` to look up `/.flatpak-info`, but that seems like a net correctness improvement, since we don't expect the FEX-Emu rootfs to override that file anyway. Other than that, no functional change intended. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Improve collection of os-release(5) info See merge request !613
-
Ludovico de Nittis authored
Distinguish between direct I/O and sysroots See merge request !612
-
- Oct 23, 2023
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Originally part of !602, follow-up for !595. Since we now have the original content of the JSON manifest in memory for Vulkan and EGL drivers (and EGL external platforms), we might we might as well write it out directly, instead of re-serializing it. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Now that we correctly read the emulated /etc/os-release in a FEX-Emu environment, we should also report the real OS somewhere. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Previously, s-r-system-info would inspect the live system looking for host OS information, even if it was meant to be parsing a JSON report and not looking at any live data. This needs to be fixed before we can add diagnostic messages to the OS info part of the JSON report, otherwise diagnostic messages from failing to find information about the host OS would become part of the loaded and re-serialized report, causing the round-trip test to fail. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
In the load/save round-trip test, this requires re-saving the file with --verbose, otherwise these fields will be lost. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
In a subsequent commit this will let us serialize additional fields. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Unlike SrtOsRelease and its accessors in SrtSystemInfo, this keeps track of everything we might want to add to the JSON report: all os-release(5) fields (not just the important ones), the source path from which we got the information, and any diagnostic messages we logged while collecting it. Because this is a separate object, it'll be more suitable for representing the various contexts that might have an os-release(5). When using FEX-Emu and pressure-vessel, we can have up to four os-release(5) files: the one that is read by native ARM code, the one in the interpreter root pseudo-overlayfs that is read by x86 code, the one that would be read by native ARM code outside the pressure-vessel container, and the one that would be read by x86 code outside the pressure-vessel container. Representing these as four objects with the same API will result in much less duplication. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
We will want this in order to be able to report whether we have found the "right" os-release when running under FEX-Emu. steamrt/tasks#342 Signed-off-by:
Simon McVittie <smcv@collabora.com>
-