Instead of https://gitlab.winehq.org/wine/wine/-/merge_requests/9108, creating D3D runtime descriptors from the Vulkan info doesn't seem possible for some cases as some information have been lost (multiple stencil formats end up with the same Vulkan format, D3D bind flags transformation is not bijective).
A separate, Wine-specific, D3DKMTEscape code will be exposed instead, to let D3D runtime implementations update the resource descriptors with the data they expect to find (ideally, the same descriptors as native, so importing can be compatible), after having been created and exported.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/9115
On Tue Oct 7 08:46:40 2025 +0000, Rémi Bernon wrote:
> IIUC `ime_ui_update_window` is always called from the IME UI window
> procedure, which is created lazily, in `get_ime_ui_window`. I think it's
> meant to live in the same thread as the activated context window but I
> don't remember the logic very well here. I'm thinking maybe the IME UI
> window should rather be destroyed then re-created in the proper thread,
> if the IME context target window thread changes?
You're right — indeed, `ime_ui_update_window` is always called from the IME UI window procedure.\
My suggestion is that we should **not** modify `ctx->hWnd` directly here, as this would cause inconsistencies between the `hWnd` and the associated `IMC`.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/9097#note_117773
This implements setting `ThreadPriorityBoost`, `ProcessPriorityBoost`, `ProcessBasePriority` and getting `ThreadPriorityBoost`, `ProcessPriorityBoost` NT info classes and adds tests where appropriate.
The actual boosting mechanism will be in part 2 to keep the size of this MR manageable.
--
v3: kernel32/tests: Add tests for GetProcessPriorityBoost/SetProcessPriorityBoost.
kernelbase: Implement SetProcessPriorityBoost.
kernelbase: Implement GetProcessPriorityBoost.
ntdll: Implement ProcessPriorityBoost class in NtSetInformationProcess.
ntdll: Implement ProcessPriorityBoost class in NtQueryInformationProcess.
ntdll: Implement ThreadPriorityBoost class in NtSetInformationThread.
ntdll: Properly implement ThreadPriorityBoost class in NtQueryInformationThread.
ntdll/tests: Add tests for setting process base priority.
ntdll: Implement ProcessBasePriority class in NtSetInformationProcess.
https://gitlab.winehq.org/wine/wine/-/merge_requests/7869
This now accounts for system suspend periods on Linux, similar to how native win32 ticks work.
On macOS `mach_continuous_time` already does so.
~~On BSDs (and other POSIX compliant operating systems) `CLOCK_MONOTONIC` likewise includes suspend time. However they also provide a `CLOCK_BOOTTIME`, which does *not* include suspend time, hence the added `__linux__` check there.~~
See https://lkml.org/lkml/2020/5/8/1707
--
v3: ntdll: Switch to CLOCK_BOOTTIME for monotonic counters when available.
https://gitlab.winehq.org/wine/wine/-/merge_requests/8916
This now accounts for system suspend periods on Linux, similar to how native win32 ticks work.
On macOS `mach_continuous_time` already does so.
~~On BSDs (and other POSIX compliant operating systems) `CLOCK_MONOTONIC` likewise includes suspend time. However they also provide a `CLOCK_BOOTTIME`, which does *not* include suspend time, hence the added `__linux__` check there.~~
See https://lkml.org/lkml/2020/5/8/1707
--
v2: ntdll: Switch to CLOCK_BOOTTIME for monotonic counters when available.
https://gitlab.winehq.org/wine/wine/-/merge_requests/8916