mirror of
https://github.com/Motorhead1991/qemu.git
synced 2025-08-02 23:33:54 -06:00
55a3f666b4
This means handling the new exit reason for Xen but still crashing on purpose. As we implement each of the hypercalls we will then return the right return code. Signed-off-by: Joao Martins <joao.m.martins@oracle.com> [dwmw2: Add CPL to hypercall tracing, disallow hypercalls from CPL > 0] Signed-off-by: David Woodhouse <dwmw@amazon.co.uk> Reviewed-by: Paul Durrant <paul@xen.org>
130 lines
3.8 KiB
C
130 lines
3.8 KiB
C
/*
|
|
* Xen HVM emulation support in KVM
|
|
*
|
|
* Copyright © 2019 Oracle and/or its affiliates. All rights reserved.
|
|
* Copyright © 2022 Amazon.com, Inc. or its affiliates. All Rights Reserved.
|
|
*
|
|
* This work is licensed under the terms of the GNU GPL, version 2 or later.
|
|
* See the COPYING file in the top-level directory.
|
|
*
|
|
*/
|
|
|
|
#include "qemu/osdep.h"
|
|
#include "qemu/log.h"
|
|
#include "sysemu/kvm_int.h"
|
|
#include "sysemu/kvm_xen.h"
|
|
#include "kvm/kvm_i386.h"
|
|
#include "xen-emu.h"
|
|
#include "trace.h"
|
|
|
|
int kvm_xen_init(KVMState *s, uint32_t hypercall_msr)
|
|
{
|
|
const int required_caps = KVM_XEN_HVM_CONFIG_HYPERCALL_MSR |
|
|
KVM_XEN_HVM_CONFIG_INTERCEPT_HCALL | KVM_XEN_HVM_CONFIG_SHARED_INFO;
|
|
struct kvm_xen_hvm_config cfg = {
|
|
.msr = hypercall_msr,
|
|
.flags = KVM_XEN_HVM_CONFIG_INTERCEPT_HCALL,
|
|
};
|
|
int xen_caps, ret;
|
|
|
|
xen_caps = kvm_check_extension(s, KVM_CAP_XEN_HVM);
|
|
if (required_caps & ~xen_caps) {
|
|
error_report("kvm: Xen HVM guest support not present or insufficient");
|
|
return -ENOSYS;
|
|
}
|
|
|
|
if (xen_caps & KVM_XEN_HVM_CONFIG_EVTCHN_SEND) {
|
|
struct kvm_xen_hvm_attr ha = {
|
|
.type = KVM_XEN_ATTR_TYPE_XEN_VERSION,
|
|
.u.xen_version = s->xen_version,
|
|
};
|
|
(void)kvm_vm_ioctl(s, KVM_XEN_HVM_SET_ATTR, &ha);
|
|
|
|
cfg.flags |= KVM_XEN_HVM_CONFIG_EVTCHN_SEND;
|
|
}
|
|
|
|
ret = kvm_vm_ioctl(s, KVM_XEN_HVM_CONFIG, &cfg);
|
|
if (ret < 0) {
|
|
error_report("kvm: Failed to enable Xen HVM support: %s",
|
|
strerror(-ret));
|
|
return ret;
|
|
}
|
|
|
|
s->xen_caps = xen_caps;
|
|
return 0;
|
|
}
|
|
|
|
int kvm_xen_init_vcpu(CPUState *cs)
|
|
{
|
|
int err;
|
|
|
|
/*
|
|
* The kernel needs to know the Xen/ACPI vCPU ID because that's
|
|
* what the guest uses in hypercalls such as timers. It doesn't
|
|
* match the APIC ID which is generally used for talking to the
|
|
* kernel about vCPUs. And if vCPU threads race with creating
|
|
* their KVM vCPUs out of order, it doesn't necessarily match
|
|
* with the kernel's internal vCPU indices either.
|
|
*/
|
|
if (kvm_xen_has_cap(EVTCHN_SEND)) {
|
|
struct kvm_xen_vcpu_attr va = {
|
|
.type = KVM_XEN_VCPU_ATTR_TYPE_VCPU_ID,
|
|
.u.vcpu_id = cs->cpu_index,
|
|
};
|
|
err = kvm_vcpu_ioctl(cs, KVM_XEN_VCPU_SET_ATTR, &va);
|
|
if (err) {
|
|
error_report("kvm: Failed to set Xen vCPU ID attribute: %s",
|
|
strerror(-err));
|
|
return err;
|
|
}
|
|
}
|
|
|
|
return 0;
|
|
}
|
|
|
|
uint32_t kvm_xen_get_caps(void)
|
|
{
|
|
return kvm_state->xen_caps;
|
|
}
|
|
|
|
static bool do_kvm_xen_handle_exit(X86CPU *cpu, struct kvm_xen_exit *exit)
|
|
{
|
|
uint16_t code = exit->u.hcall.input;
|
|
|
|
if (exit->u.hcall.cpl > 0) {
|
|
exit->u.hcall.result = -EPERM;
|
|
return true;
|
|
}
|
|
|
|
switch (code) {
|
|
default:
|
|
return false;
|
|
}
|
|
}
|
|
|
|
int kvm_xen_handle_exit(X86CPU *cpu, struct kvm_xen_exit *exit)
|
|
{
|
|
if (exit->type != KVM_EXIT_XEN_HCALL) {
|
|
return -1;
|
|
}
|
|
|
|
if (!do_kvm_xen_handle_exit(cpu, exit)) {
|
|
/*
|
|
* Some hypercalls will be deliberately "implemented" by returning
|
|
* -ENOSYS. This case is for hypercalls which are unexpected.
|
|
*/
|
|
exit->u.hcall.result = -ENOSYS;
|
|
qemu_log_mask(LOG_UNIMP, "Unimplemented Xen hypercall %"
|
|
PRId64 " (0x%" PRIx64 " 0x%" PRIx64 " 0x%" PRIx64 ")\n",
|
|
(uint64_t)exit->u.hcall.input,
|
|
(uint64_t)exit->u.hcall.params[0],
|
|
(uint64_t)exit->u.hcall.params[1],
|
|
(uint64_t)exit->u.hcall.params[2]);
|
|
}
|
|
|
|
trace_kvm_xen_hypercall(CPU(cpu)->cpu_index, exit->u.hcall.cpl,
|
|
exit->u.hcall.input, exit->u.hcall.params[0],
|
|
exit->u.hcall.params[1], exit->u.hcall.params[2],
|
|
exit->u.hcall.result);
|
|
return 0;
|
|
}
|