| commit | 431c51e9d48faecbd2dd3ffc49b1636f280bfe8d | |
| author | Paolo Bonzini <pbonzini@redhat.com> | |
| Fri, 16 Jun 2023 21:58:25 +0000 (16 23:58 +0200) | ||
| committer | Paolo Bonzini <pbonzini@redhat.com> | |
| Mon, 26 Jun 2023 08:23:07 +0000 (26 10:23 +0200) | ||
| tree | 3f848c63601747247493030cd80ca7610b862fcd | treesnapshot (tar.gz zip) |
| parent | 1420dd6a19cfbdf444af5622797d5d95a24d9461 | commitdiff |
target/i386: TCG supports WBNOINVD
WBNOINVD is the same as INVD or WBINVD as far as TCG is concerned,
since there is no cache in TCG and therefore no invalidation side effect
in WBNOINVD.
With respect to SVM emulation, processors that do not support WBNOINVD
will ignore the prefix and treat it as WBINVD, while those that support
it will generate exactly the same vmexit.
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
WBNOINVD is the same as INVD or WBINVD as far as TCG is concerned,
since there is no cache in TCG and therefore no invalidation side effect
in WBNOINVD.
With respect to SVM emulation, processors that do not support WBNOINVD
will ignore the prefix and treat it as WBINVD, while those that support
it will generate exactly the same vmexit.
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
| target/i386/cpu.c | diffblobblamehistory | |
| target/i386/tcg/translate.c | diffblobblamehistory |