The commit is pushed to "branch-rh10-6.12.0-55.52.1.5.x.vz10-ovz" and will 
appear at [email protected]:openvz/vzkernel.git
after rh10-6.12.0-55.52.1.5.29.vz10
------>
commit 08824f1d838c2020d05426bab5a90b6e2e9d43a3
Author: Vladimir Riabchun <[email protected]>
Date:   Tue Jun 2 21:10:45 2026 +0000

    fixup! /proc/<pid>/vz_latency: Show maximal allocation latency in the last 
2min.
    
    Move KSTAT_ALLOC_MAX_LAT_PERIOD outside CONFIG_VE.
    
    https://virtuozzo.atlassian.net/browse/VSTOR-130116
    
    Feature: !CONFIG_VE build
    Signed-off-by: Vladimir Riabchun <[email protected]>
    Reviewed-by: Vasileios Almpanis <[email protected]>
---
 include/linux/vzstat.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/include/linux/vzstat.h b/include/linux/vzstat.h
index 4a5738bd036fa..aed334a59f687 100644
--- a/include/linux/vzstat.h
+++ b/include/linux/vzstat.h
@@ -43,6 +43,8 @@ extern spinlock_t kstat_glb_lock;
 
 extern void kstat_init(void);
 
+#define KSTAT_ALLOC_MAX_LAT_PERIOD (120*HZ)
+
 #ifdef CONFIG_VE
 extern void KSTAT_PERF_ADD(struct kstat_perf_pcpu_struct *ptr, u64 real_time,
                           u64 cpu_time);
@@ -58,8 +60,6 @@ extern void KSTAT_PERF_ADD(struct kstat_perf_pcpu_struct 
*ptr, u64 real_time,
        sleep_time = current->se.statistics->sum_sleep_runtime - sleep_time; \
        KSTAT_PERF_ADD(&kstat_glob.name, start, start - sleep_time);
 
-#define KSTAT_ALLOC_MAX_LAT_PERIOD (120*HZ)
-
 static inline u64 get_max_lat(struct kstat_lat_snap_struct *snap)
 {
        int i;
_______________________________________________
Devel mailing list
[email protected]
https://lists.openvz.org/mailman/listinfo/devel

Reply via email to