public inbox for qemu-devel@nongnu.org
 help / color / mirror / Atom feed
From: Mohamed Mediouni <mohamed@unpredictable.fr>
To: qemu-devel@nongnu.org
Cc: Mohamed Mediouni <mohamed@unpredictable.fr>,
	Wei Liu <wei.liu@kernel.org>,
	Phil Dennis-Jordan <phil@philjordan.eu>,
	Pedro Barbuda <pbarbuda@microsoft.com>,
	Roman Bolshakov <rbolshakov@ddn.com>
Subject: [PATCH 00/12] whpx: i386: Windows 10 and performance fixes
Date: Mon, 23 Mar 2026 20:36:33 +0100	[thread overview]
Message-ID: <20260323193645.82602-1-mohamed@unpredictable.fr> (raw)

On Windows 10, the paravirtualisation enlightenments aren't available.
And neither is performance monitoring. Using the former as a gate to
operate in a reduced-functionality mode on Windows 10.

And on the performance side, some state is really expensive to fetch
or write with Hyper-V so switch some less-essential state to on demand.

The effect of this is magnified on Windows 10 because Hyper-V enlightenments
are not available there.

Issue number: https://gitlab.com/qemu-project/qemu/-/work_items/3349

Mohamed Mediouni (12):
  whpx: i386: workaround for Windows 10 support
  whpx: i386: enable exceptions VM exit only when needed
  whpx: i386: skip TSC read for MMIO exits
  whpx: i386: skip XCRs read for MMIO exits
  whpx: i386: don't restore segment registers after MMIO handling
  target/i386: emulate: add new callbacks
  whpx: i386: add implementation of new x86_emul_ops
  target/i386: emulate: indirect access to CRs
  whpx: i386: indirect access to CRs
  target/i386: emulate: segmentation rework
  whpx: i386: fetch segments on-demand
  whpx: i386: fast runtime state reads

 target/i386/emulate/x86_emu.h     |   6 +
 target/i386/emulate/x86_helpers.c |  84 +++++-----
 target/i386/emulate/x86_mmu.c     |  11 +-
 target/i386/whpx/whpx-all.c       | 263 +++++++++++++++++++++++++-----
 4 files changed, 274 insertions(+), 90 deletions(-)

-- 
2.50.1 (Apple Git-155)



             reply	other threads:[~2026-03-23 19:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 19:36 Mohamed Mediouni [this message]
2026-03-23 19:36 ` [PATCH 01/12] whpx: i386: workaround for Windows 10 support Mohamed Mediouni
2026-03-23 19:36 ` [PATCH 02/12] whpx: i386: enable exceptions VM exit only when needed Mohamed Mediouni
2026-03-23 19:36 ` [PATCH 03/12] whpx: i386: skip TSC read for MMIO exits Mohamed Mediouni
2026-03-23 19:36 ` [PATCH 04/12] whpx: i386: skip XCRs " Mohamed Mediouni
2026-03-23 19:36 ` [PATCH 05/12] whpx: i386: don't restore segment registers after MMIO handling Mohamed Mediouni
2026-03-23 19:36 ` [PATCH 06/12] target/i386: emulate: add new callbacks Mohamed Mediouni
2026-03-23 19:36 ` [PATCH 07/12] whpx: i386: add implementation of new x86_emul_ops Mohamed Mediouni
2026-03-23 19:36 ` [PATCH 08/12] target/i386: emulate: indirect access to CRs Mohamed Mediouni
2026-03-23 19:36 ` [PATCH 09/12] whpx: i386: " Mohamed Mediouni
2026-03-23 19:36 ` [PATCH 10/12] target/i386: emulate: segmentation rework Mohamed Mediouni
2026-03-23 19:36 ` [PATCH 11/12] whpx: i386: fetch segments on-demand Mohamed Mediouni
2026-03-23 19:36 ` [PATCH 12/12] whpx: i386: fast runtime state reads Mohamed Mediouni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260323193645.82602-1-mohamed@unpredictable.fr \
    --to=mohamed@unpredictable.fr \
    --cc=pbarbuda@microsoft.com \
    --cc=phil@philjordan.eu \
    --cc=qemu-devel@nongnu.org \
    --cc=rbolshakov@ddn.com \
    --cc=wei.liu@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox