Re: [Xen-devel] [PATCH v19 12/14] x86/VPMU: Merge vpmu_rdmsr and vpmu_wrmsr

>>> On 17.03.15 at 15:54, wrote: > --- > Changes in v19: > * const-ified arch_vpmu_ops in vpmu_do_wrmsr > * non-changes: >- kept 'current' as a non-initializer to avoid unnecessary initialization > in the (common) non-VPMU case Afaict there's nothing at all keeping the compiler to still

Re: [Xen-devel] [PATCH v19 12/14] x86/VPMU: Merge vpmu_rdmsr and vpmu_wrmsr

Am Mittwoch 25 März 2015, 09:29:14 schrieb Dietmar Hahn: > Am Dienstag 17 März 2015, 10:54:09 schrieb Boris Ostrovsky: > > The two routines share most of their logic. > > > > Signed-off-by: Boris Ostrovsky > > --- > > Changes in v19: > > * const-ified arch_vpmu_ops in vpmu_do_wrmsr > > * non-chan

Re: [Xen-devel] [PATCH v19 12/14] x86/VPMU: Merge vpmu_rdmsr and vpmu_wrmsr

Am Dienstag 17 März 2015, 10:54:09 schrieb Boris Ostrovsky: > The two routines share most of their logic. > > Signed-off-by: Boris Ostrovsky > --- > Changes in v19: > * const-ified arch_vpmu_ops in vpmu_do_wrmsr > * non-changes: >- kept 'current' as a non-initializer to avoid unnecessary init

[Xen-devel] [PATCH v19 12/14] x86/VPMU: Merge vpmu_rdmsr and vpmu_wrmsr

The two routines share most of their logic. Signed-off-by: Boris Ostrovsky --- Changes in v19: * const-ified arch_vpmu_ops in vpmu_do_wrmsr * non-changes: - kept 'current' as a non-initializer to avoid unnecessary initialization in the (common) non-VPMU case - kept 'nop' label since th