On 19 Jun 2016, at 21:54, Peter Maydell wrote:
> The purpose of the get/put functions, broadly, is "copy
> state from the hypervisor into QEMU's cpu state struct
> and vice-versa". The specific details are down to KVM's ABI
> (and to historical details like some KVM ioctls being newer
> or optio
On 19 June 2016 at 20:36, Alex Bligh wrote:
> Looking at kvm_arch_put_registers it appears to be pretty complicated.
> It appears to 'put' each individual register type, as well as putting
> an xsave region. I'm a bit confused why the ordinary registers 'put'
> are not then overwritten by the xsav
I'm still plugging away at my Hypervisor.Framework port (now rewritten
to be another accelerator like kvm).
It appears to be setting up memory regions, and I'm now working on
the equivalent of kvm_cpu_exec. I see an exit code 33 on the first
call, which is an invalid VMCS. This is unsurprising as
