Li, Fei1 5d6c9c33ca hv: vlapic: clear up where needs atomic operation in vLAPIC ... In almost case, vLAPIC will only be accessed by the related vCPU. There's no synchronization issue in this case. However, other vCPUs could deliver interrupts to the current vCPU, in this case, the IRR (for APICv base situation) or PIR (for APICv advanced situation) and TMR for both cases could be accessed by more than one vCPUS simultaneously. So operations on IRR or PIR should be atomical and visible to other vCPUs immediately. In another case, vLAPIC could be accessed by another vCPU when create vCPU or reset vCPU which could be supposed to be consequently. Tracked-On: #1842 Signed-off-by: Li, Fei1 <fei1.li@intel.com>		2019-07-11 09:15:47 +08:00
..
arch/x86	hv: vlapic: clear up where needs atomic operation in vLAPIC	2019-07-11 09:15:47 +08:00
common	hv: ptdev: refine ptdev active flag	2019-07-03 17:44:45 +08:00
debug	hv: bugfix for sbuf reset	2019-06-27 15:40:19 +08:00
dm	HV: fix vuart.c "Parameter needs to add const"	2019-07-09 10:36:44 +08:00
hw	HV: add support for 64-bit bar emulation	2019-07-04 11:25:01 +08:00
lib	hv:move several files related X86 for lib	2019-05-13 10:12:20 +08:00
public	DM/HV: Increase VM name len	2019-05-27 12:13:51 +08:00