Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1906209yba; Thu, 25 Apr 2019 07:35:57 -0700 (PDT) X-Google-Smtp-Source: APXvYqyK9EmajdrT8u5/I3Nw0+3qy4oqs2TmPDy++XWpD45Vc29eep9bst0WjzpEEfyWCJ6WsPa6 X-Received: by 2002:a65:5089:: with SMTP id r9mr37334041pgp.14.1556202957199; Thu, 25 Apr 2019 07:35:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556202957; cv=none; d=google.com; s=arc-20160816; b=zw38VRw3qstE2i6HlHHJ54P7fB+6JODJsG5j9cegBVYhK8QYBD/cdHvcRsv++42DgG GmORiXiUJtlV2Ns/wh7onptwDrW8QXn7T9lBv2dYtAPj6ENDfl9HaieCEhRpvlAu8Jd7 nT26Ztak0aWXZIDPDYoVUcMWUBhOQPZsIgvRI2vbheHYGBlze5bx/ygfugxk+rxQZ3wB oeNpSebbkv/ggrFjfKP5SaZQTqdOUfZNLiDdPNMP0tft8OieUvtVp9odmMdOnLx2cgcM q/sqyfWJNFHbAvUCJ74OZJ/7UV1DyiCUsnCU9ZAVRh23vx54lVGEdZzkJ5d/+LH2ZaG7 IR0w== 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=L+bC8L/rk+AebmvzU2SLyxDQuQS2DLOxwrPg90K4PWI=; b=IWuKn1dMLEoKScN0DHgkhQLbJWD9sbNN42w1uJTV1YL3CNUbvfoJgbdfPkK0iwxAK3 sek6Cf8Mv+4dcJ/cyySJf9I1UGwg28VPHp3HopmWrmZp9FQPkmbAPvaObtXJQSg2B6/y a2yVQT0uZQfdPTkByDBItlO0alZ0ViZmA+XAUNVSLPjvfTqKYxS0FCD8OntgPWQAA+FM Q455X5oF6kBsOETRPr5+6Y81PiipogR9nOUxXJWVacCRBBAcRR4bJrEJmdA2pBSc4tLg Exuvyd+aQecPjRFX0QJgeP3/1nWxhGrIMkTRw0S0MN7i9ssOnLokfXOblEY1ufkGECe3 yrcA== 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 61si22716137plf.290.2019.04.25.07.35.41; Thu, 25 Apr 2019 07:35:57 -0700 (PDT) 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 S1727012AbfDYOdc (ORCPT + 99 others); Thu, 25 Apr 2019 10:33:32 -0400 Received: from mga17.intel.com ([192.55.52.151]:50006 "EHLO mga17.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725900AbfDYOdb (ORCPT ); Thu, 25 Apr 2019 10:33:31 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Apr 2019 07:33:30 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,394,1549958400"; d="scan'208";a="134317356" Received: from aubrey-skl.sh.intel.com ([10.239.53.6]) by orsmga007.jf.intel.com with ESMTP; 25 Apr 2019 07:33:28 -0700 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, adobriyan@gmail.com, akpm@linux-foundation.org, aubrey.li@intel.com, linux-api@vger.kernel.org, linux-kernel@vger.kernel.org, Aubrey Li , Andy Lutomirski Subject: [PATCH v18 2/3] x86,/proc/pid/arch_status: Add AVX-512 usage elapsed time Date: Thu, 25 Apr 2019 22:32:18 +0800 Message-Id: <20190425143219.102258-2-aubrey.li@linux.intel.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20190425143219.102258-1-aubrey.li@linux.intel.com> References: <20190425143219.102258-1-aubrey.li@linux.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. Tensorflow example: $ while [ 1 ]; do cat /proc/tid/arch_status | grep AVX512; sleep 1; done AVX512_elapsed_ms: 4 AVX512_elapsed_ms: 8 AVX512_elapsed_ms: 4 This means that 4 milliseconds have elapsed since the AVX512 usage of tensorflow task was detected when the task was scheduled out. Or: $ cat /proc/tid/arch_status | grep AVX512 AVX512_elapsed_ms: -1 The number '-1' indicates that no AVX512 usage recorded before thus the task 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: Thomas Gleixner Cc: Peter Zijlstra Cc: Andi Kleen Cc: Tim Chen Cc: Dave Hansen Cc: Arjan van de Ven Cc: Alexey Dobriyan Cc: Andrew Morton Cc: Andy Lutomirski Cc: Linux API --- arch/x86/Kconfig | 1 + arch/x86/kernel/fpu/xstate.c | 47 ++++++++++++++++++++++++++++++++++++ 2 files changed, 48 insertions(+) diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig index 5ad92419be19..d5a9c5ddd453 100644 --- a/arch/x86/Kconfig +++ b/arch/x86/Kconfig @@ -208,6 +208,7 @@ config X86 select USER_STACKTRACE_SUPPORT select VIRT_TO_BUS select X86_FEATURE_NAMES if PROC_FS + select PROC_PID_ARCH_STATUS if PROC_FS config INSTRUCTION_DECODER def_bool y diff --git a/arch/x86/kernel/fpu/xstate.c b/arch/x86/kernel/fpu/xstate.c index d7432c2b1051..fcaaf21aa015 100644 --- a/arch/x86/kernel/fpu/xstate.c +++ b/arch/x86/kernel/fpu/xstate.c @@ -7,6 +7,8 @@ #include #include #include +#include +#include #include #include @@ -1243,3 +1245,48 @@ int copy_user_to_xstate(struct xregs_state *xsave, const void __user *ubuf) return 0; } + +#ifdef CONFIG_PROC_PID_ARCH_STATUS +/* + * Report the amount of time elapsed in millisecond since last AVX512 + * use in the task. + */ +static void avx512_status(struct seq_file *m, struct task_struct *task) +{ + unsigned long timestamp = READ_ONCE(task->thread.fpu.avx512_timestamp); + long delta; + + if (!timestamp) { + /* + * Report -1 if no AVX512 usage + */ + delta = -1; + } else { + delta = (long)(jiffies - timestamp); + /* + * Cap to LONG_MAX if time difference > LONG_MAX + */ + if (delta < 0) + delta = LONG_MAX; + delta = jiffies_to_msecs(delta); + } + + seq_put_decimal_ll(m, "AVX512_elapsed_ms:\t", delta); + seq_putc(m, '\n'); +} + +/* + * Report architecture specific information + */ +int proc_pid_arch_status(struct seq_file *m, struct pid_namespace *ns, + struct pid *pid, struct task_struct *task) +{ + /* + * Report AVX512 state if the processor and build option supported. + */ + if (cpu_feature_enabled(X86_FEATURE_AVX512F)) + avx512_status(m, task); + + return 0; +} +#endif /* CONFIG_PROC_PID_ARCH_STATUS */ -- 2.17.1