From: Launchpad Bug Tracker <1574346@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1574346] Re: TCG: mov to segment register is incorrectly emulated for AMD CPUs
Date: Tue, 22 Jun 2021 04:18:52 -0000 [thread overview]
Message-ID: <162433553298.20423.1340431066590334915.malone@loganberry.canonical.com> (raw)
In-Reply-To: 20160424174546.5288.30510.malonedeb@chaenomeles.canonical.com
[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/1574346
Title:
TCG: mov to segment register is incorrectly emulated for AMD CPUs
Status in QEMU:
Expired
Bug description:
In TCG mode, the effect of:
xorl %eax, %eax
movl %eax, %gs
is to mark the GS segment unusable and set its base to zero. After
doing this, reading MSR_GS_BASE will return zero and using a GS prefix
in long mode will treat the GS base as zero.
This is correct for Intel CPUs but is incorrect for AMD CPUs. On an
AMD CPU, writing 0 to %gs using mov, pop, or (I think) lgs will leave
the base unchanged.
To make it easier to use TCG to validate behavior on different CPUs,
please consider changing the TCG behavior to match actual CPU behavior
when emulating an AMD CPU.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1574346/+subscriptions
prev parent reply other threads:[~2021-06-22 5:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-24 17:45 [Qemu-devel] [Bug 1574346] [NEW] TCG: mov to segment register is incorrectly emulated for AMD CPUs Andy Lutomirski
2016-04-24 20:07 ` [Qemu-devel] [Bug 1574346] " pranith
2021-04-22 9:35 ` Thomas Huth
2021-06-22 4:18 ` Launchpad Bug Tracker [this message]
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=162433553298.20423.1340431066590334915.malone@loganberry.canonical.com \
--to=1574346@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).