Re: [Xen-devel] [PATCH 2/2] x86/VPMU: Handle APIC_LVTPC accesses

2015-01-29 Thread Jan Beulich
>>> On 29.01.15 at 16:28, wrote: > However, if you insist on dropping all tags even for minor changes like > that (and "determining what "minor" is is a judgment call) I will > certainly do that in the future. I don't mind you (and others) keeping them for minor changes. But a small change isn'

Re: [Xen-devel] [PATCH 2/2] x86/VPMU: Handle APIC_LVTPC accesses

2015-01-29 Thread Boris Ostrovsky
On 01/29/2015 06:54 AM, Jan Beulich wrote: On 28.01.15 at 20:56, wrote: Don't have the hypervisor update APIC_LVTPC when _it_ thinks the vector should be updated. Instead, handle guest's APIC_LVTPC accesses and write what the guest explicitly wanted (but only when VPMU is enabled). This is upd

Re: [Xen-devel] [PATCH 2/2] x86/VPMU: Handle APIC_LVTPC accesses

2015-01-29 Thread Jan Beulich
>>> On 28.01.15 at 20:56, wrote: > Don't have the hypervisor update APIC_LVTPC when _it_ thinks the vector > should be updated. Instead, handle guest's APIC_LVTPC accesses and write > what > the guest explicitly wanted (but only when VPMU is enabled). > > This is updated version of commit 809761

[Xen-devel] [PATCH 2/2] x86/VPMU: Handle APIC_LVTPC accesses

2015-01-28 Thread Boris Ostrovsky
Don't have the hypervisor update APIC_LVTPC when _it_ thinks the vector should be updated. Instead, handle guest's APIC_LVTPC accesses and write what the guest explicitly wanted (but only when VPMU is enabled). This is updated version of commit 8097616fbdda that was reverted by cc3404093c85. Unlik