From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] x86/core changes for v5.3
Date: Mon, 8 Jul 2019 18:11:42 +0200 [thread overview]
Message-ID: <20190708161142.GA107326@gmail.com> (raw)
Linus,
Please pull the latest x86-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-core-for-linus
# HEAD: 711486fd18596315d42cebaac3dba8c408f60a3d Documentation/filesystems/proc.txt: Add arch_status file
This adds a new ABI that the main scheduler probably doesn't want to deal
with but HPC job schedulers might want to use, the AVX512_elapsed_ms
field in the new /proc/<pid>/arch_status task status file, which allows
the user-space job scheduler to cluster such tasks, to avoid turbo
frequency drops.
out-of-topic modifications in x86-core-for-linus:
---------------------------------------------------
fs/proc/Kconfig # 68bc30bb9f33: proc: Add /proc/<pid>/arch_s
fs/proc/base.c # 68bc30bb9f33: proc: Add /proc/<pid>/arch_s
include/linux/proc_fs.h # 68bc30bb9f33: proc: Add /proc/<pid>/arch_s
Thanks,
Ingo
------------------>
Aubrey Li (3):
proc: Add /proc/<pid>/arch_status
x86/process: Add AVX-512 usage elapsed time to /proc/pid/arch_status
Documentation/filesystems/proc.txt: Add arch_status file
Documentation/filesystems/proc.txt | 40 ++++++++++++++++++++++++++++++++
arch/x86/Kconfig | 1 +
arch/x86/kernel/fpu/xstate.c | 47 ++++++++++++++++++++++++++++++++++++++
fs/proc/Kconfig | 4 ++++
fs/proc/base.c | 6 +++++
include/linux/proc_fs.h | 9 ++++++++
6 files changed, 107 insertions(+)
next reply other threads:[~2019-07-08 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 16:11 Ingo Molnar [this message]
2019-07-09 1:45 ` [GIT PULL] x86/core changes for v5.3 pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190708161142.GA107326@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).