From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Tamas K Lengyel <tlengyel@novetta.com>, xen-devel@lists.xenproject.org
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Keir Fraser <keir@xen.org>, Jan Beulich <jbeulich@suse.com>,
Razvan Cojocaru <rcojocaru@bitdefender.com>
Subject: Re: [PATCH] vm_event: consolidate hvm_event_fill_regs and p2m_vm_event_fill_regs
Date: Thu, 11 Feb 2016 21:35:42 +0000 [thread overview]
Message-ID: <56BCFEAE.8070608@citrix.com> (raw)
In-Reply-To: <1455224749-2120-1-git-send-email-tlengyel@novetta.com>
On 11/02/2016 21:05, Tamas K Lengyel wrote:
> diff --git a/xen/arch/x86/vm_event.c b/xen/arch/x86/vm_event.c
> index 08d678a..fa5d154 100644
> --- a/xen/arch/x86/vm_event.c
> +++ b/xen/arch/x86/vm_event.c
> @@ -122,6 +122,64 @@ void vm_event_set_registers(struct vcpu *v, vm_event_response_t *rsp)
> v->arch.user_regs.eip = rsp->data.regs.x86.rip;
> }
>
> +void vm_event_fill_regs(vm_event_request_t *req)
> +{
> + const struct cpu_user_regs *regs = guest_cpu_user_regs();
> + struct segment_register seg;
> + struct hvm_hw_cpu ctxt;
> + struct vcpu *curr = current;
> +
> + req->data.regs.x86.rax = regs->eax;
> + req->data.regs.x86.rcx = regs->ecx;
> + req->data.regs.x86.rdx = regs->edx;
> + req->data.regs.x86.rbx = regs->ebx;
> + req->data.regs.x86.rsp = regs->esp;
> + req->data.regs.x86.rbp = regs->ebp;
> + req->data.regs.x86.rsi = regs->esi;
> + req->data.regs.x86.rdi = regs->edi;
> +
> + req->data.regs.x86.r8 = regs->r8;
> + req->data.regs.x86.r9 = regs->r9;
> + req->data.regs.x86.r10 = regs->r10;
> + req->data.regs.x86.r11 = regs->r11;
> + req->data.regs.x86.r12 = regs->r12;
> + req->data.regs.x86.r13 = regs->r13;
> + req->data.regs.x86.r14 = regs->r14;
> + req->data.regs.x86.r15 = regs->r15;
> +
> + req->data.regs.x86.rflags = regs->eflags;
> + req->data.regs.x86.rip = regs->eip;
> + req->data.regs.x86.dr7 = curr->arch.debugreg[7];
I think there is a %dr7 handling issue here. For an HVM guests, this
field is only valid when you are not in the context of the guest, as it
lives in the vmcs/vmcs. (PV guests keep it synchronously up to date)
Normally, the vcpu context switch code takes care of calling
{vmx,svm}_{save,restore}_dr(), which is why migration works fine (not
permitted in the context of the guest), you are now introducing a new path.
I think you need to modify {vmx,svm}_{vmcb,vmcs}_save() to do a
selective {vmx,svm}_save_dr() if v == current.
~Andrew
next prev parent reply other threads:[~2016-02-11 21:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 21:05 [PATCH] vm_event: consolidate hvm_event_fill_regs and p2m_vm_event_fill_regs Tamas K Lengyel
2016-02-11 21:35 ` Andrew Cooper [this message]
2016-02-11 21:49 ` Razvan Cojocaru
2016-02-11 21:58 ` Andrew Cooper
2016-02-11 22:25 ` Lengyel, Tamas
2016-02-11 22:30 ` Andrew Cooper
2016-02-11 22:38 ` Lengyel, Tamas
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=56BCFEAE.8070608@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=rcojocaru@bitdefender.com \
--cc=tlengyel@novetta.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 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.