[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <13430819.uLZWGnKmhe@grey>
Date: Wed, 03 Jan 2024 10:30:24 +0300
From: Stefan Dösinger <stefan@...eweavers.com>
To: x86@...nel.org, Linux Kernel <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
Borislav Petkov <bp@...en8.de>, Dave Hansen <dave.hansen@...ux.intel.com>,
Ricardo Neri <ricardo.neri-calderon@...ux.intel.com>, wine-devel@...ehq.org,
"H. Peter Anvin" <hpa@...or.com>
Cc: Elizabeth Figura <zfigura@...eweavers.com>
Subject: Re: x86 SGDT emulation for Wine
Am Dienstag, 2. Januar 2024, 22:53:26 EAT schrieb Elizabeth Figura:
> I'm concerned that this will be very expensive. Most VM users don't need
> to exit on every syscall. While I haven't tested KVM, I think some other
> Wine developers actually did a similar experiment using a hypervisor to
> solve some other problem (related to 32-bit support on Mac OS), and exiting
> the hypervisor was prohibitively slow.
Just to add to this point, Ken Thomases and I experimented with this on Mac
OS, and as Zeb said, we found it to be unworkably slow. In the d3d games we
tested the performance of hypervisor + lots of exits was approximately the
same as running all 32 bit guest code inside qemu's software CPU emulation, or
about 5% of the performance of using native 32 bit mac processes (when they
still existed). From what we could tell the cost was imposed by the CPU and
not MacOS' very lightweight hypervisor API.
There are obviously differences between Mac and Linux, and with Wine's new
syscalls we probably don't need to exit as often as my hangover wrapper DLLs
did, but combined with the other reasons Zeb listed I don't think running Wine
inside KVM is ever going to be realistic.
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists