#
b3a1f5f1 |
| 26-Nov-2020 |
Samuel Ortiz <sameo@linux.intel.com> |
hypervisor: Start moving register definitions to the hypervisor crate
Most of arch/src/x86_64/regs.rs will eventually move unde hypervisor/src/x86/regs.rs.
Signed-off-by: Samuel Ortiz <sameo@linux.
hypervisor: Start moving register definitions to the hypervisor crate
Most of arch/src/x86_64/regs.rs will eventually move unde hypervisor/src/x86/regs.rs.
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
show more ...
|
#
1fc97e91 |
| 19-Nov-2020 |
Samuel Ortiz <sameo@linux.intel.com> |
hypervisor: x86: Add an InstructionHandler interface
And an InstructionMap helper structure to map x86 mnemonic codes to instruction handlers.
Any instruction emulation implementation should then b
hypervisor: x86: Add an InstructionHandler interface
And an InstructionMap helper structure to map x86 mnemonic codes to instruction handlers.
Any instruction emulation implementation should then boil down with implementing InstructionHandler for any supported mnemonic.
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
show more ...
|
#
546778eb |
| 13-Nov-2020 |
Samuel Ortiz <sameo@linux.intel.com> |
hypervisor: x86: Add a CpuStateManager interface
For efficiently emulating x86 instructions, we need to build and pass a CPU state copy/reference to instruction emulation handlers. Those handlers wi
hypervisor: x86: Add a CpuStateManager interface
For efficiently emulating x86 instructions, we need to build and pass a CPU state copy/reference to instruction emulation handlers. Those handlers will typically modify the CPU state and let the caller commit those changes back through the PlatformEmulator trait set_cpu_state method.
Hypervisors typically have internal CPU state structures, that maps back to the correspinding kernel APIs. By implementing the CpuState trait, instruction emulators will be able to directly work on CPU state instances that are directly consumable by the underlying hypervisor and its kernel APIs.
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
show more ...
|
#
ae96aeda |
| 13-Nov-2020 |
Samuel Ortiz <sameo@linux.intel.com> |
arch: Move the gdt module to the hypervisor crate
We will need the GDT API for the hypervisor's x86 instruction emulator implementation, it's better if the arch crate depends on the hypervisor one r
arch: Move the gdt module to the hypervisor crate
We will need the GDT API for the hypervisor's x86 instruction emulator implementation, it's better if the arch crate depends on the hypervisor one rather than the other way around.
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
show more ...
|
#
2518b9e3 |
| 28-Jun-2020 |
Wei Liu <liuwe@microsoft.com> |
vmm: hypervisor: fix white space issues
Signed-off-by: Wei Liu <liuwe@microsoft.com>
|
#
72ae1577 |
| 26-Jun-2020 |
Muminul Islam <muislam@microsoft.com> |
hypervisor: Update license to Apache-2.0 OR BSD-3-Clause
Initially the licensing was just Apache-2.0. This patch changes the licensing to dual license Apache-2.0 OR BSD-3-Clause
Signed-off-by: Mumi
hypervisor: Update license to Apache-2.0 OR BSD-3-Clause
Initially the licensing was just Apache-2.0. This patch changes the licensing to dual license Apache-2.0 OR BSD-3-Clause
Signed-off-by: Muminul Islam <muislam@microsoft.com>
show more ...
|
#
c48d0c1a |
| 02-Jun-2020 |
Muminul Islam <muislam@microsoft.com> |
hypervisor: kvm: Implement vCPU state method
Implement the vCPU state getter and setter separately from the initial KVM Hypervisor trait implementation, mostly for readability purposes.
Signed-off-
hypervisor: kvm: Implement vCPU state method
Implement the vCPU state getter and setter separately from the initial KVM Hypervisor trait implementation, mostly for readability purposes.
Signed-off-by: Muminul Islam <muislam@microsoft.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
show more ...
|
#
72e39a34 |
| 03-Jun-2020 |
Muminul Islam <muislam@microsoft.com> |
hypervisor: Add KVM implementation
For each of the traits we are defining kvm related structures and add the trait implementation to the structs. For more information please see the kvm-ioctls and k
hypervisor: Add KVM implementation
For each of the traits we are defining kvm related structures and add the trait implementation to the structs. For more information please see the kvm-ioctls and kvm-bindings crate.
This is a standalone implementation that does not include the switch of the Cloud-Hypervisor vmm and arch crates to it.
Signed-off-by: Muminul Islam <muislam@microsoft.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
show more ...
|