| History log of /src/sys/modules/vmt/Makefile |
| Revision | | Date | Author | Comments |
| 1.5 |
| 09-May-2024 |
pho | port-arm/58194: Resurrect vmt(4) from bitrot
On this architecture vmt(4) used to search for a node "/hypervisor" in the
FDT and probed the VMware hypervisor call only when the node was
found. However, things appear to have changed and VMware no longer provides
the FDT node.
Since vmt(4) doesn't actually need to read anything from FDT, and the
hypervisor call logically resides in virtual CPUs themselves, it would be
better to attach it directly to cpu, just like how it's probed on x86.
|
| 1.4 |
| 27-Oct-2020 |
ryo | move vmt(4) from MD to MI, and add support vmt on aarch64. tested on ESXi-Arm Fling
- move from sys/arch/x86/x86/{vmt.c,vmtreg.h,vmtvar.h} to sys/dev/vmt/{vmt_subr.c,vmtreg.h,vmtvar.h},
and split the attach part of the cpufeaturebus and fdt
- add aarch64 vmware backdoor op
- add include guard to vmt{reg,var}.h
- Yet there is still some little-endian dependency. it needs to be fixed in order to work properly on aarch64eb
|
| 1.3 |
| 17-Feb-2019 |
rin | Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.
Also, turn on -Wno-missing-noreturn for clang for some files.
At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5
Discussed on tech-kern.
|
| 1.2 |
| 20-Oct-2011 |
jmcneill | branches: 1.2.54;
mark vm_reg members as volatile instead of building this with -O0
|
| 1.1 |
| 17-Oct-2011 |
jmcneill | add a port of the VMware Tools driver vmt(4) from OpenBSD
|
| 1.2.54.1 |
| 10-Jun-2019 |
christos | Sync with HEAD
|
