Re: Helping Wine use 64 bit Mesa OGL drivers for 32-bit Windows applications

2024-10-22 Thread Derek Lesho
Am 10/21/24 um 11:35 schrieb Michel Dänzer: And Wine's solution for this can't be implemented in Mesa? I think this might actually be possible: In order to accomplish this Wine essentially keeps calling mmaps with addresses in its range until it finds a free spot. It of course is able to alr

Re: Helping Wine use 64 bit Mesa OGL drivers for 32-bit Windows applications

2024-10-22 Thread James Jones
This sounds interesting, but does it come with the same "Only gets 2GB VA" downside Derek pointed out in the thread fork where he was responding to Michel? Thanks, -James On 10/22/24 07:14, Christian König wrote: Hi guys, one theoretical alternative not mentioned in this thread is the use of

Re: Helping Wine use 64 bit Mesa OGL drivers for 32-bit Windows applications

2024-10-22 Thread Christian König
Hi guys, one theoretical alternative not mentioned in this thread is the use of mremap(). In other words you reserve some address space below 2G by using mmap(NULL, length, PROT_NONE, MAP_32BIT | MAP_ANONYMOUS, 0, 0) and then use mremap(addr64bit, 0, length, MREMAP_FIXED, reserved_addr). I

Re: Helping Wine use 64 bit Mesa OGL drivers for 32-bit Windows applications

2024-10-22 Thread Jose Fonseca
So, it sounds like something like an OpenGL equivalent of VK_EXT_map_memory_placed would be more palatable? While we're at it, something like VK_EXT_map_memory_placed that also allows to place the GPU resource handles (not host VAs) could be used by https://github.com/apitrace/apitrace to try repl