|
From: | Richard Henderson |
Subject: | Re: [RFC PATCH 06/16] target/arm/kvm-rme: Initialize vCPU |
Date: | Fri, 27 Jan 2023 12:37:12 -1000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 |
On 1/27/23 05:07, Jean-Philippe Brucker wrote:
+static int kvm_arm_rme_get_core_regs(CPUState *cs) +{ + int i, ret; + struct kvm_one_reg reg; + ARMCPU *cpu = ARM_CPU(cs); + CPUARMState *env = &cpu->env; + + for (i = 0; i < 8; i++) { + reg.id = AARCH64_CORE_REG(regs.regs[i]); + reg.addr = (uintptr_t) &env->xregs[i]; + ret = kvm_vcpu_ioctl(cs, KVM_GET_ONE_REG, ®); + if (ret) { + return ret; + } + } + + return 0; +}
Wow, this is quite the restriction.I get that this is just enough to seed the guest for boot, and take SMC traps, but I'm concerned that we can't do much with the machine underneath, when it comes to other things like "info registers" or gdbstub will be silently unusable. I would prefer if we can somehow make this loudly unusable.
Pardon if I'm jumping the gun and you handle this later. r~
[Prev in Thread] | Current Thread | [Next in Thread] |