[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug 1904317] Re: cpu feature selection is not affected to guest 's cpui
From: |
Launchpad Bug Tracker |
Subject: |
[Bug 1904317] Re: cpu feature selection is not affected to guest 's cpuid with whpx |
Date: |
Sat, 10 Jul 2021 04:17:16 -0000 |
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1904317
Title:
cpu feature selection is not affected to guest 's cpuid with whpx
Status in QEMU:
Expired
Bug description:
On windows with -accel whpx, "-cpu" is ignored without any messages.
Guest recognizes features as same as host's.
Confirmed on v5.2.0-rc1.
I suggest qemu may do,
- Warn with incompatible -cpu options were given.
- Enhance cpuid handling.
Background:
I was investigated mmio and block copy issue in Linux kernel.
I met a problem that Linux went ill for touching mmio with whpx. (not with
tcg)
I suspect erms(enhanced rep movs) might trigger.
I tried to mask erms on qemu with -feature,erms, but it was ineffective.
At last, I disabled erms manually, to tweak whpx-all.c to mask erms in
cpuid.
FYI, qemu with whpx from/to mmio, "rep movsb" does byte access regardless of
erms.
Linux kernel tends to choose not "rep movsq" but "rep movsb" with erms.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1904317/+subscriptions
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug 1904317] Re: cpu feature selection is not affected to guest 's cpuid with whpx,
Launchpad Bug Tracker <=