We do not intercept xsetbv on AMD - and we don't need to. Thus there is
no need to handle related VM exits.

Signed-off-by: Jan Kiszka <[email protected]>
---
 hypervisor/arch/x86/svm.c | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/hypervisor/arch/x86/svm.c b/hypervisor/arch/x86/svm.c
index 8ffc5aa..0a536d0 100644
--- a/hypervisor/arch/x86/svm.c
+++ b/hypervisor/arch/x86/svm.c
@@ -965,10 +965,6 @@ void vcpu_handle_exit(struct per_cpu *cpu_data)
                                goto vmentry;
                }
                break;
-       case VMEXIT_XSETBV:
-               if (vcpu_handle_xsetbv())
-                       goto vmentry;
-               break;
        case VMEXIT_IOIO:
                cpu_data->stats[JAILHOUSE_CPU_STAT_VMEXITS_PIO]++;
                if (vcpu_handle_io_access())
-- 
2.1.4

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to