From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Kevin Tian <kevin.tian@intel.com>, Jun Nakajima <jun.nakajima@intel.com>
Subject: Re: [PATCH] x86/VMX: use unambiguous register names
Date: Tue, 3 Jan 2017 13:08:33 +0000 [thread overview]
Message-ID: <5802a85c-f4a8-dbbb-a9c9-0a9d097a1763@citrix.com> (raw)
In-Reply-To: <586BAEAE020000780012C9CF@prv-mh.provo.novell.com>
On 03/01/17 13:01, Jan Beulich wrote:
> @@ -1321,10 +1321,10 @@ static void virtual_vmexit(struct cpu_us
> if ( lm_l1 != lm_l2 )
> paging_update_paging_modes(v);
>
> - regs->eip = get_vvmcs(v, HOST_RIP);
> - regs->esp = get_vvmcs(v, HOST_RSP);
> + regs->rip = get_vvmcs(v, HOST_RIP);
> + regs->rsp = get_vvmcs(v, HOST_RSP);
> /* VM exit clears all bits except bit 1 */
> - regs->eflags = 0x2;
> + regs->rflags = 0x2;
With this updated to X86_EFLAGS_MBS,
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-01-03 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 13:01 [PATCH] x86/VMX: use unambiguous register names Jan Beulich
2017-01-03 13:08 ` Andrew Cooper [this message]
2017-01-05 2:46 ` Tian, Kevin
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=5802a85c-f4a8-dbbb-a9c9-0a9d097a1763@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=xen-devel@lists.xenproject.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).