John Baldwin 44a68c4e40 - Rework the XSAVE/XRSTOR emulation to only expose XCR0 features to the ... guest for which the rules regarding xsetbv emulation are known. In particular future extensions like AVX-512 have interdependencies among feature bits that could allow a guest to trigger a GP# in the host with the current approach of allowing anything the host supports. - Add proper checking of Intel MPX and AVX-512 XSAVE features in the xsetbv emulation and allow these features to be exposed to the guest if they are enabled in the host. - Expose a subset of known-safe features from leaf 0 of the structured extended features to guests if they are supported on the host including RDFSBASE/RDGSBASE, BMI1/2, AVX2, AVX-512, HLE, ERMS, and RTM. Aside from AVX-512, these features are all new instructions available for use in ring 3 with no additional hypervisor changes needed. Reviewed by: neel		2014-05-27 19:04:38 +00:00
..
acpica	Consistently use round_page(x) rather than roundup(x, PAGE_SIZE). There is	2013-02-15 22:43:08 +00:00
amd64	Don't permit users to request a subset of the AVX512 or MPX xsave masks.	2014-05-22 18:22:02 +00:00
conf	imagact_binmisc builds for all supported architectures, so enable it for all.	2014-05-22 05:04:40 +00:00
ia32	x86: Allow users to change PSL_RF via ptrace(PT_SETREGS...)	2013-11-14 15:37:20 +00:00
include	Add segment protection and limits violation checks in vie_calculate_gla()	2014-05-27 04:26:22 +00:00
linux32	Update kernel inclusions of capability.h to use capsicum.h instead; some	2014-03-16 10:55:57 +00:00
pci	Fix undefined behavior: (1 << 31) is not defined as 1 is an int and this	2013-11-30 22:17:27 +00:00
vmm	- Rework the XSAVE/XRSTOR emulation to only expose XCR0 features to the	2014-05-27 19:04:38 +00:00
Makefile