Zhao Yakui e4a3a63496 acrn/vhm: change the default notification vector to 0xF3 ... Currently the SOS kernel will call hcall_set_callback_vector to config the expected up-notification vector(0xF3) and then hypervisor uses the passed vector to raise the interrupt to SOS when needed. As sos kernel already switches to 0xF3 notification vector, the default notification vector can be changed from 0xF7 to 0xF3. In such case it still can work well even when the SOS kernel doesn't reconfigure the notification vector. Tracked-On: projectacrn/acrn-hypervisor#2355 Acked-by: Eddie Dong <eddie.dong@intel.com> Signed-off-by: Zhao Yakui <yakui.zhao@intel.com>		2019-01-18 11:04:22 +08:00
..
hv_main.c	hv: hv_main: adjust vm exit trace position	2019-01-16 10:24:33 +08:00
hypercall.c	acrn/vhm: change the default notification vector to 0xF3	2019-01-18 11:04:22 +08:00
io_request.c	acrn/vhm: change the default notification vector to 0xF3	2019-01-18 11:04:22 +08:00
ptdev.c	hv: ptdev: fix MISRAC violations	2018-12-20 09:08:57 +08:00
schedule.c	hv: clean the "Procedure has more than one exit point".	2019-01-08 14:47:01 +08:00
softirq.c	hv: remove the theoretic infinite loop	2018-12-05 13:17:38 +08:00
stack_protector.c	HV:common:fix "expression is not Boolean"	2018-06-20 14:19:47 +08:00
static_checks.c	hv: use int32_t replace int	2018-12-12 13:08:10 +08:00
trusty_hypercall.c	hv: tursty_hypercall: fix "Procedure has more than one exit point"	2018-12-27 09:04:32 +08:00
vm_load.c	hv: fix sprintf and hypercall violations	2018-12-25 16:33:13 +08:00