|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [PATCH 02/11] x86/vPMU: avoid effectively open-coding xzalloc_flex_struct()
There is a difference in generated code: xzalloc_bytes() forces
SMP_CACHE_BYTES alignment. I think we not only don't need this here, but
actually don't want it.
Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
--- a/xen/arch/x86/cpu/vpmu_intel.c
+++ b/xen/arch/x86/cpu/vpmu_intel.c
@@ -461,10 +461,10 @@ static int core2_vpmu_alloc_resource(str
goto out_err;
}
- core2_vpmu_cxt = xzalloc_bytes(sizeof(*core2_vpmu_cxt) +
- sizeof(uint64_t) * fixed_pmc_cnt +
- sizeof(struct xen_pmu_cntr_pair) *
- arch_pmc_cnt);
+ core2_vpmu_cxt = xzalloc_flex_struct(struct xen_pmu_intel_ctxt, regs,
+ fixed_pmc_cnt + arch_pmc_cnt *
+ (sizeof(struct xen_pmu_cntr_pair) /
+ sizeof(*core2_vpmu_cxt->regs)));
p = xzalloc(uint64_t);
if ( !core2_vpmu_cxt || !p )
goto out_err;
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |