>>> On 24.03.15 at 16:47, wrote:
> On 03/24/2015 11:36 AM, Jan Beulich wrote:
> On 24.03.15 at 16:13, wrote:
>>> On 03/24/2015 10:28 AM, Jan Beulich wrote:
>>> On 17.03.15 at 15:54, wrote:
> Changes in v19:
> * Adjusted for new ops interfaces (passing vcpu vs. vpmu)
> * Test
On 03/24/2015 11:36 AM, Jan Beulich wrote:
On 24.03.15 at 16:13, wrote:
On 03/24/2015 10:28 AM, Jan Beulich wrote:
On 17.03.15 at 15:54, wrote:
Changes in v19:
* Adjusted for new ops interfaces (passing vcpu vs. vpmu)
* Test for domain->max_cpu in choose_hwdom_vcpu() instead of
'domain->vcpu
>>> On 24.03.15 at 16:13, wrote:
> On 03/24/2015 10:28 AM, Jan Beulich wrote:
> On 17.03.15 at 15:54, wrote:
>>> Changes in v19:
>>> * Adjusted for new ops interfaces (passing vcpu vs. vpmu)
>>> * Test for domain->max_cpu in choose_hwdom_vcpu() instead of
>>> 'domain->vcpu!=NULL'
>> I suppose
On 03/24/2015 10:28 AM, Jan Beulich wrote:
On 17.03.15 at 15:54, wrote:
Changes in v19:
* Adjusted for new ops interfaces (passing vcpu vs. vpmu)
* Test for domain->max_cpu in choose_hwdom_vcpu() instead of
'domain->vcpu!=NULL'
I suppose that's something that then should also be done in patch
>>> On 17.03.15 at 15:54, wrote:
> Changes in v19:
> * Adjusted for new ops interfaces (passing vcpu vs. vpmu)
> * Test for domain->max_cpu in choose_hwdom_vcpu() instead of
> 'domain->vcpu!=NULL'
I suppose that's something that then should also be done in patch 7?
> --- a/xen/arch/x86/hvm/vpmu
Add support for handling PMU interrupts for PV guests.
VPMU for the interrupted VCPU is unloaded until the guest issues XENPMU_flush
hypercall. This allows the guest to access PMU MSR values that are stored in
VPMU context which is shared between hypervisor and domain, thus avoiding
traps to hyper
