From: Alexandru Isaila <aisaila@bitdefender.com>
To: xen-devel@lists.xen.org
Cc: tamas@tklengyel.com, suravee.suthikulpanit@amd.com,
rcojocaru@bitdefender.com, andrew.cooper3@citrix.com,
jbeulich@suse.com, Alexandru Isaila <aisaila@bitdefender.com>,
boris.ostrovsky@oracle.com
Subject: [PATCH v3] hvm/svm: Implement CPUID events
Date: Fri, 23 Feb 2018 11:46:56 +0200 [thread overview]
Message-ID: <1519379216-9929-1-git-send-email-aisaila@bitdefender.com> (raw)
At this moment the CPUID events for the AMD architecture are not
forwarded to the monitor layer.
This patch adds the CPUID event to the common capabilities and then
forwards the event to the monitor layer.
---
Changes since V2:
- Pass the inst_len to svm_vmexit_do_cpuid()
Signed-off-by: Alexandru Isaila <aisaila@bitdefender.com>
---
xen/arch/x86/hvm/svm/svm.c | 27 ++++++++++++++++++---------
xen/include/asm-x86/monitor.h | 2 +-
2 files changed, 19 insertions(+), 10 deletions(-)
diff --git a/xen/arch/x86/hvm/svm/svm.c b/xen/arch/x86/hvm/svm/svm.c
index e36ad05..8ae2ae5 100644
--- a/xen/arch/x86/hvm/svm/svm.c
+++ b/xen/arch/x86/hvm/svm/svm.c
@@ -1799,19 +1799,15 @@ static void svm_fpu_dirty_intercept(void)
vmcb_set_cr0(vmcb, vmcb_get_cr0(vmcb) & ~X86_CR0_TS);
}
-static void svm_vmexit_do_cpuid(struct cpu_user_regs *regs)
+static int svm_vmexit_do_cpuid(struct cpu_user_regs *regs, unsigned int inst_len)
{
struct vcpu *curr = current;
- unsigned int inst_len;
struct cpuid_leaf res;
- if ( (inst_len = __get_instruction_length(curr, INSTR_CPUID)) == 0 )
- return;
-
if ( hvm_check_cpuid_faulting(curr) )
{
hvm_inject_hw_exception(TRAP_gp_fault, 0);
- return;
+ return 1; /* Don't advance the guest IP! */
}
guest_cpuid(curr, regs->eax, regs->ecx, &res);
@@ -1822,7 +1818,7 @@ static void svm_vmexit_do_cpuid(struct cpu_user_regs *regs)
regs->rcx = res.c;
regs->rdx = res.d;
- __update_guest_eip(regs, inst_len);
+ return hvm_monitor_cpuid(inst_len, regs->eax, regs->ecx);
}
static void svm_vmexit_do_cr_access(
@@ -2768,9 +2764,22 @@ void svm_vmexit_handler(struct cpu_user_regs *regs)
}
case VMEXIT_CPUID:
- svm_vmexit_do_cpuid(regs);
- break;
+ {
+ unsigned int inst_len = __get_instruction_length(v, INSTR_CPUID);
+ int rc = 0;
+ if ( inst_len == 0 )
+ break;
+
+ rc = svm_vmexit_do_cpuid(regs, inst_len);
+
+ if ( rc < 0 )
+ goto unexpected_exit_type;
+ if ( !rc )
+ __update_guest_eip(regs, inst_len); /* Safe: CPUID */
+
+ break;
+ }
case VMEXIT_HLT:
svm_vmexit_do_hlt(vmcb, regs);
break;
diff --git a/xen/include/asm-x86/monitor.h b/xen/include/asm-x86/monitor.h
index 7a9e1e8..99ed4b87 100644
--- a/xen/include/asm-x86/monitor.h
+++ b/xen/include/asm-x86/monitor.h
@@ -81,12 +81,12 @@ static inline uint32_t arch_monitor_get_capabilities(struct domain *d)
(1U << XEN_DOMCTL_MONITOR_EVENT_SOFTWARE_BREAKPOINT) |
(1U << XEN_DOMCTL_MONITOR_EVENT_MOV_TO_MSR) |
(1U << XEN_DOMCTL_MONITOR_EVENT_INTERRUPT) |
+ (1U << XEN_DOMCTL_MONITOR_EVENT_CPUID) |
(1U << XEN_DOMCTL_MONITOR_EVENT_WRITE_CTRLREG));
if ( cpu_has_vmx )
{
capabilities |= ((1U << XEN_DOMCTL_MONITOR_EVENT_DEBUG_EXCEPTION) |
- (1U << XEN_DOMCTL_MONITOR_EVENT_CPUID) |
(1U << XEN_DOMCTL_MONITOR_EVENT_EMUL_UNIMPLEMENTED));
/* Since we know this is on VMX, we can just call the hvm func */
--
2.7.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2018-02-23 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 9:46 Alexandru Isaila [this message]
2018-02-23 14:50 ` [PATCH v3] hvm/svm: Implement CPUID events Boris Ostrovsky
2018-02-23 22:27 ` Tamas K Lengyel
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=1519379216-9929-1-git-send-email-aisaila@bitdefender.com \
--to=aisaila@bitdefender.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jbeulich@suse.com \
--cc=rcojocaru@bitdefender.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tamas@tklengyel.com \
--cc=xen-devel@lists.xen.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).