- 05 Jul, 2023 17 commits
-
-
Alistair Leslie-Hughes authored
-
Alistair Leslie-Hughes authored
-
Alistair Leslie-Hughes authored
-
Alistair Leslie-Hughes authored
-
Alistair Leslie-Hughes authored
-
Alistair Leslie-Hughes authored
-
Alistair Leslie-Hughes authored
-
Alistair Leslie-Hughes authored
-
Alistair Leslie-Hughes authored
-
Alistair Leslie-Hughes authored
-
Alistair Leslie-Hughes authored
-
Alistair Leslie-Hughes authored
-
Alistair Leslie-Hughes authored
-
Alistair Leslie-Hughes authored
-
Alistair Leslie-Hughes authored
-
Alistair Leslie-Hughes authored
-
Alistair Leslie-Hughes authored
-
- 04 Jul, 2023 23 commits
-
-
Alex Henrie authored
-
Alex Henrie authored
-
Kevin Schmidt authored
-
Jiajin Cui authored
If the length of wszApplicationName exceeds 1024, it will cause an error when writing to the subsequent stack space after exceeding the wcmd space, Wcmd needs to be modified to dynamic allocation. Signed-off-by: Jiajin Cui <cuijiajin@uniontech.com>
-
Billy Laws authored
-
Billy Laws authored
-
Billy Laws authored
4.18+ Linux kernels remove support for IPX but keep SOL_IPX defined, which causes compilation errors as wine unconditionally uses IPX structures if this is the case. Instead check for IPX_MTU to determine IPX support as it is defined within the ipx.h header itself.
-
Vladislav Timonin authored
-
Vladislav Timonin authored
-
Matteo Bruni authored
And do some mandatory cleanup while at it.
-
Matteo Bruni authored
-
Matteo Bruni authored
-
Matteo Bruni authored
And give a good clean up to the test and all its helpers.
-
Matteo Bruni authored
-
Matteo Bruni authored
-
Matteo Bruni authored
-
Matteo Bruni authored
-
Eric Pouech authored
-
Matteo Bruni authored
Otherwise it fails for me on 32-bit Linux with my current compiler.
-
Zebediah Figura authored
This shouldn't really make a difference, but does make the code a bit conceptually simpler.
-
Zebediah Figura authored
Allocating and freeing fences in particular can be expensive, as much as 250 µs per call (observed on an NVidia machine).
-
Zebediah Figura authored
-
Matteo Bruni authored
Over the last few Wine releases we greatly reduced the need for the application thread to wait for replies from the CS thread. Compared to the time when the command stream was initially introduced, it's now quite likely that, when the command queues become empty, they are going to stay like that for a while (e.g. the game is throttling the framerate or is busy doing some CPU work on its part before generating more commands). As a first step, reduce the spin count to reduce the busy waiting in wined3d_cs_run(). In my tests this significantly reduces CPU usage, with minimally decreased performance in a few rare cases but also significantly improved performance in many cases (notably with integrated GPUs where freeing the CPU directly allows more power to be allocated to the GPU).
-