From: Andre Przywara <andre.przywara@amd.com>
To: avi@redhat.com
Cc: kvm@vger.kernel.org, Andre Przywara <andre.przywara@amd.com>
Subject: [PATCH] kvm: always set accessed bit in VMCS segment selectors
Date: Fri, 9 Jan 2009 13:02:36 +0100 [thread overview]
Message-ID: <1231502556706-git-send-email-andre.przywara@amd.com> (raw)
Intel manual 22.3.1.2 demands that the accessed bit (bit 0 in type field)
must be set when on DS,ES,FS and GS when the selector is usable.
This fixes cross vendor migration from AMD to Intel.
I am not sure what the real purpose of this check is, so I put this
in the VMX path and not in the SVM one. If someone has an explanation
which justifies a move, I am happy to do this.
Signed-off-by: Andre Przywara <andre.przywara@amd.com>
---
arch/x86/kvm/vmx.c | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 9b56d21..d19e39c 100644
--- a/arch/x86/kvm/vmx.c
+++ b/arch/x86/kvm/vmx.c
@@ -1723,6 +1723,11 @@ static void vmx_set_segment(struct kvm_vcpu *vcpu,
ar = 0xf3;
} else
ar = vmx_segment_access_rights(var);
+
+ /* 22.3.1.2 demands that the accessed bit must be set on [DEFG]S */
+ if (var->s && (sf->ar_bytes & AR_UNUSABLE_MASK) == 0)
+ ar |= 0x1;
+
vmcs_write32(sf->ar_bytes, ar);
}
--
1.5.2.2
next reply other threads:[~2009-01-09 12:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 12:02 Andre Przywara [this message]
2009-01-09 17:57 ` [PATCH] kvm: always set accessed bit in VMCS segment selectors Avi Kivity
2009-01-09 21:27 ` [PATCH] set accessed bit for VMCB " Andre Przywara
2009-01-10 5:17 ` Amit Shah
2009-01-11 21:39 ` [PATCH] kvm: " Andre Przywara
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=1231502556706-git-send-email-andre.przywara@amd.com \
--to=andre.przywara@amd.com \
--cc=avi@redhat.com \
--cc=kvm@vger.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