events/intel/core.c

2918  * We may be running with guest PEBS events created by KVM, and the
2919  * PEBS records are logged into the guest's DS and invisible to host.
2921  * In the case of guest PEBS overflow, we only trigger a fake event
2922  * to emulate the PEBS overflow PMI for guest PEBS counters in KVM.
2923  * The guest will then vm-entry and check the guest DS area to read
2924  * the guest PEBS records.
2926  * The contents and other behavior of the guest event do not matter.
4108  *	.host = the value the hardware has when it doesn't run a guest,
4109  *	.guest = the value the hardware has when it runs a guest,
4112  * These values have nothing to do with the emulated values the guest sees
4127 	 * used for PEBS when running a guest, because PEBS writes to virtual
4135 		.guest = intel_ctrl & ~cpuc->intel_ctrl_host_mask & ~pebs_mask,
4143 	 * disable counter on a guest entry since PEBS memory
4144 	 * write can overshoot guest entry and corrupt guest
4153 			.guest = 0,
4164 		.guest = kvm_pmu->ds_area,
4171 			.guest = kvm_pmu->pebs_data_cfg,
4179 		.guest = pebs_mask & ~cpuc->intel_ctrl_host_mask,
4183 		/* Disable guest PEBS if host PEBS is enabled. */
4184 		arr[pebs_enable].guest = 0;
4186 		/* Disable guest PEBS thoroughly for cross-mapped PEBS counters. */
4187 		arr[pebs_enable].guest &= ~kvm_pmu->host_cross_mapped_mask;
4188 		arr[global_ctrl].guest &= ~kvm_pmu->host_cross_mapped_mask;
4189 		/* Set hw GLOBAL_CTRL bits for PEBS counter when it runs for guest */
4190 		arr[global_ctrl].guest |= arr[pebs_enable].guest;
4206 		arr[idx].host = arr[idx].guest = 0;
4211 		arr[idx].host = arr[idx].guest =
4217 			arr[idx].guest &= ~ARCH_PERFMON_EVENTSEL_ENABLE;