Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3753572imu; Tue, 18 Dec 2018 03:42:20 -0800 (PST) X-Google-Smtp-Source: AFSGD/XQByXuH2Hp9x7Qgv5s2a3S1gnU6vzs1PoeYmg5dhTe0l2vjAllMxUKkVma1osUQWRrNx0m X-Received: by 2002:a17:902:22f:: with SMTP id 44mr16003298plc.137.1545133340674; Tue, 18 Dec 2018 03:42:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1545133340; cv=none; d=google.com; s=arc-20160816; b=MhdVmjqkRV0yMEX8nWRfE579I8oeSgx5RerOZbmAArclJXtIsE4dLj911npZqHym55 aBHmNxYIcpfaiI+zYzk356klfMHjPRN0/XFiSinM3Sl+lPVmSIfogUEiGchwhSzMdw39 pUSdYGBLRS4+A8Y+0LPDk6oiagb/nfiBsZ/XK33ve5ePoP+WkCLhnytJgg5Pf9bp31Lp WAhkp9uEwMW3Gbbv74L50sy54/QZq3BpK7c6UoC/Nw3g21CxJqtsfhFhUFKGjcKpFs+9 ew0TduIrwu2RMzlYxnXn03WwHAnh1EK0MKHURwKVd+ah1x9PEE1YVlvHtPUmTEpfPqfV d9sw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from; bh=sexk4nblloJsgke4WwfLlUw3oD68Q6YbM1i4RAxgI58=; b=o7ssDdnCKyIKXdbdfb8HowS4gwAVkaPbik1jwkUaMwN/AnIDA+7lW5INli7FAzd7SW nPO0lAmzf/r0Bg17YchuIxsA3KDdCt8C8Ai2THKzw2Eqt+0EnKRBJHNa3A4T9mlpy17M fYG2YIqHkdsStVsCnpjhkDjIA8cx5bCNWH2cJZ7ZrS+fW5hdIMh0fw6iPhibSS0oavLU B0ihpzsX3tt96aKzlW+ctfBGlzW4gD+QIy66dWH+weULH4qWcLEYv7Hk2TY1bcvtJd7o nfTooYTbOgeteqgw1n4MLg8sNrNuHilQgvWp7KExCCJT45LJF5y/kMi70nPHQR+wF3aP z8yg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f7si13319744pga.87.2018.12.18.03.42.05; Tue, 18 Dec 2018 03:42:20 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726721AbeLRLkx (ORCPT + 99 others); Tue, 18 Dec 2018 06:40:53 -0500 Received: from mga03.intel.com ([134.134.136.65]:62099 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726583AbeLRLki (ORCPT ); Tue, 18 Dec 2018 06:40:38 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Dec 2018 03:40:38 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,367,1539673200"; d="scan'208";a="304764717" Received: from aubrey-skl.sh.intel.com ([10.239.53.9]) by fmsmga005.fm.intel.com with ESMTP; 18 Dec 2018 03:40:36 -0800 From: Aubrey Li To: tglx@linutronix.de, mingo@redhat.com, peterz@infradead.org, hpa@zytor.com Cc: ak@linux.intel.com, tim.c.chen@linux.intel.com, dave.hansen@intel.com, arjan@linux.intel.com, aubrey.li@intel.com, linux-kernel@vger.kernel.org, Aubrey Li Subject: [PATCH v6 2/3] proc: add AVX-512 usage elapsed time to /proc/pid/status Date: Tue, 18 Dec 2018 12:22:17 +0800 Message-Id: <20181218042218.8653-2-aubrey.li@intel.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20181218042218.8653-1-aubrey.li@intel.com> References: <20181218042218.8653-1-aubrey.li@intel.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org AVX-512 components use could cause core turbo frequency drop. So it's useful to expose AVX-512 usage elapsed time as a heuristic hint for the user space job scheduler to cluster the AVX-512 using tasks together. Example: $ cat /proc/pid/status | grep AVX512_elapsed_ms AVX512_elapsed_ms: 1020 The number '1020' denotes 1020 millisecond elapsed since last time context switch the off-CPU task using AVX-512 components, thus the task could cause core frequency drop. Or: $ cat /proc/pid/status | grep AVX512_elapsed_ms AVX512_elapsed_ms: -1 The number '-1' indicates the task didn't use AVX-512 components before thus unlikely has frequency drop issue. User space tools may want to further check by: $ perf stat --pid -e core_power.lvl2_turbo_license -- sleep 1 Performance counter stats for process id '3558': 3,251,565,961 core_power.lvl2_turbo_license 1.004031387 seconds time elapsed Non-zero counter value confirms that the task causes frequency drop. Signed-off-by: Aubrey Li Cc: Peter Zijlstra Cc: Andi Kleen Cc: Tim Chen Cc: Dave Hansen Cc: Arjan van de Ven --- arch/x86/kernel/fpu/xstate.c | 34 ++++++++++++++++++++++++++++++++++ fs/proc/array.c | 5 +++++ 2 files changed, 39 insertions(+) diff --git a/arch/x86/kernel/fpu/xstate.c b/arch/x86/kernel/fpu/xstate.c index 87a57b7642d3..d084b1dc80a6 100644 --- a/arch/x86/kernel/fpu/xstate.c +++ b/arch/x86/kernel/fpu/xstate.c @@ -7,6 +7,7 @@ #include #include #include +#include #include #include @@ -1245,3 +1246,36 @@ int copy_user_to_xstate(struct xregs_state *xsave, const void __user *ubuf) return 0; } + +/* + * Report the amount of time elapsed in millisecond since last AVX512 + * use in the task. + */ +void avx512_state(struct seq_file *m, struct task_struct *task) +{ + u64 timestamp = task->thread.fpu.avx512_timestamp; + s64 delta; + + if (!timestamp) + delta = -1; + else { + WARN_ON_ONCE(jiffies_64 < timestamp); + delta = div_u64(jiffies64_to_nsecs(jiffies_64 - timestamp), + NSEC_PER_MSEC); + } + + seq_put_decimal_ll(m, "AVX512_elapsed_ms:\t", delta); + seq_putc(m, '\n'); +} + +/* + * Report CPU specific thread state + */ +void arch_task_state(struct seq_file *m, struct task_struct *task) +{ + /* + * Report AVX512 state if the processor and build option supported. + */ + if (cpu_feature_enabled(X86_FEATURE_AVX512F)) + avx512_state(m, task); +} diff --git a/fs/proc/array.c b/fs/proc/array.c index 0ceb3b6b37e7..dd88c2219f08 100644 --- a/fs/proc/array.c +++ b/fs/proc/array.c @@ -392,6 +392,10 @@ static inline void task_core_dumping(struct seq_file *m, struct mm_struct *mm) seq_putc(m, '\n'); } +void __weak arch_task_state(struct seq_file *m, struct task_struct *task) +{ +} + int proc_pid_status(struct seq_file *m, struct pid_namespace *ns, struct pid *pid, struct task_struct *task) { @@ -414,6 +418,7 @@ int proc_pid_status(struct seq_file *m, struct pid_namespace *ns, task_cpus_allowed(m, task); cpuset_task_status_allowed(m, task); task_context_switch_counts(m, task); + arch_task_state(m, task); return 0; } -- 2.17.1