Re: [Xen-devel] [PATCH v1 3/5] xen/PMU: Initialization code for Xen PMU

2013-09-23 Thread Boris Ostrovsky
On 09/23/2013 10:18 AM, Boris Ostrovsky wrote: On 09/23/2013 09:26 AM, Konrad Rzeszutek Wilk wrote: On Tue, Sep 10, 2013 at 11:31:48AM -0400, Boris Ostrovsky wrote: Map shared data structure that will hold CPU registers, VPMU context, VCPU/PCPI IDs of the VCPU interrupted by PMU interrupt. Hype

Re: [PATCH v1 3/5] xen/PMU: Initialization code for Xen PMU

2013-09-23 Thread Boris Ostrovsky
On 09/23/2013 09:26 AM, Konrad Rzeszutek Wilk wrote: On Tue, Sep 10, 2013 at 11:31:48AM -0400, Boris Ostrovsky wrote: Map shared data structure that will hold CPU registers, VPMU context, VCPU/PCPI IDs of the VCPU interrupted by PMU interrupt. Hypervisor fills this information in its handler and

Re: [PATCH v1 3/5] xen/PMU: Initialization code for Xen PMU

2013-09-23 Thread Konrad Rzeszutek Wilk
On Tue, Sep 10, 2013 at 11:31:48AM -0400, Boris Ostrovsky wrote: > Map shared data structure that will hold CPU registers, VPMU context, > VCPU/PCPI IDs of the VCPU interrupted by PMU interrupt. Hypervisor > fills this information in its handler and passes it to the guest for > further processing.

[PATCH v1 3/5] xen/PMU: Initialization code for Xen PMU

2013-09-10 Thread Boris Ostrovsky
Map shared data structure that will hold CPU registers, VPMU context, VCPU/PCPI IDs of the VCPU interrupted by PMU interrupt. Hypervisor fills this information in its handler and passes it to the guest for further processing. Set up PMU VIRQ. Signed-off-by: Boris Ostrovsky --- arch/x86/xen/Make