From: Julian Stecklina <jsteckli@os.inf.tu-dresden.de>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: KVM VMX: register state after reset violates spec
Date: Mon, 03 Dec 2012 14:49:59 +0100 [thread overview]
Message-ID: <87624jp7nc.fsf@os.inf.tu-dresden.de> (raw)
In-Reply-To: <20121202133802.GA8731@redhat.com> (Gleb Natapov's message of "Sun, 2 Dec 2012 15:38:02 +0200")
Thus spake Gleb Natapov <gleb@redhat.com>:
> It should, so why not move the fix to kvm_vcpu_reset() so it will work
> for both. Also what about R8-R15? Intel SDM says nothing about them in
> the section you mention, but in Volume 1 section 3.4.1.1 is says:
[...]
> I take it that they are undefined on the first transition to 64-bit mode
> too. AMD spec says that they should be zeroed on reset, so lets do that.
> Also SVM does not set EDX to correct value on reset. It should be:
I have posted a new version of the patch taking your suggestions into
account. The VMX version is working for me. I could not test it on AMD
hardware, though.
Julian
prev parent reply other threads:[~2012-12-03 13:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 14:07 KVM VMX: register state after reset violates spec Julian Stecklina
2012-11-29 14:38 ` [PATCH] KVM VMX: Make register state after reset conform to specification Julian Stecklina
2012-11-29 14:55 ` Julian Stecklina
2012-12-02 13:38 ` KVM VMX: register state after reset violates spec Gleb Natapov
2012-12-03 12:05 ` Julian Stecklina
2012-12-03 13:46 ` [PATCH v2] KVM: x86: Make register state after reset conform to specification Julian Stecklina
2012-12-04 9:48 ` Gleb Natapov
2012-12-04 12:13 ` [PATCH v3] " Julian Stecklina
2012-12-05 10:50 ` Gleb Natapov
2012-12-05 12:00 ` [PATCH v4] " Julian Stecklina
2012-12-05 13:27 ` Gleb Natapov
2012-12-05 14:26 ` [PATCH v5] " Julian Stecklina
2012-12-05 16:02 ` Gleb Natapov
2012-12-05 14:27 ` [PATCH v4] " Julian Stecklina
2012-12-03 13:49 ` Julian Stecklina [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=87624jp7nc.fsf@os.inf.tu-dresden.de \
--to=jsteckli@os.inf.tu-dresden.de \
--cc=gleb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.