Re: [Xen-devel] [PATCH v18 00/16] x86/PMU: Xen PMU PV(H) support

2015-02-17 Thread Andrew Cooper
On 17/02/15 17:38, Boris Ostrovsky wrote: > On 02/17/2015 10:13 AM, Andrew Cooper wrote: >> On 16/02/15 22:26, Boris Ostrovsky wrote: >>> Changes in v18: >>> >>> * Return 1 (i.e. "handled") in vpmu_do_interrupt() if PMU_CACHED is >>>set. This is needed since we can get an interrupt while this f

Re: [Xen-devel] [PATCH v18 00/16] x86/PMU: Xen PMU PV(H) support

2015-02-17 Thread Boris Ostrovsky
On 02/17/2015 10:13 AM, Andrew Cooper wrote: On 16/02/15 22:26, Boris Ostrovsky wrote: Changes in v18: * Return 1 (i.e. "handled") in vpmu_do_interrupt() if PMU_CACHED is set. This is needed since we can get an interrupt while this flag is set on AMD processors when multiple counters are

Re: [Xen-devel] [PATCH v18 00/16] x86/PMU: Xen PMU PV(H) support

2015-02-17 Thread Andrew Cooper
On 16/02/15 22:26, Boris Ostrovsky wrote: > Changes in v18: > > * Return 1 (i.e. "handled") in vpmu_do_interrupt() if PMU_CACHED is > set. This is needed since we can get an interrupt while this flag is > set on AMD processors when multiple counters are in use (**) (AMD > processor don't mask

[Xen-devel] [PATCH v18 00/16] x86/PMU: Xen PMU PV(H) support

2015-02-16 Thread Boris Ostrovsky
Changes in v18: * Return 1 (i.e. "handled") in vpmu_do_interrupt() if PMU_CACHED is set. This is needed since we can get an interrupt while this flag is set on AMD processors when multiple counters are in use (**) (AMD processor don't mask LVTPC when PMC interrupt happens and so there is a