From: "H.J. Lu" <hjl.tools@gmail.com>
To: libc-alpha@sourceware.org
Cc: Florian Weimer <fweimer@redhat.com>, Carlos O'Donell <carlos@redhat.com>
Subject: V3 [PATCH 0/2] ld.so: Add --list-tunables to print tunable values
Date: Fri, 16 Oct 2020 18:02:05 -0700 [thread overview]
Message-ID: <20201017010207.6074-1-hjl.tools@gmail.com> (raw)
Tunable values and their minimum/maximum values are invisible to users.
This patch set adds --list-tunables to ld.so to print tunable values
with their minimum and maximum values.
--list-tunables works on i686 and x86-64. Please test --list-tunables on
your native processors. users/hjl/tunable/master branch at:
https://gitlab.com/x86-glibc/glibc/-/commits/users/hjl/tunable/master
contains the same set of patches.
On x86, to make cache info accessible to --list-tunables, they are moved
to cpu_features in ld.so and TUNABLE_SET_WITH_BOUNDS is used to update
tunable bounds.
H.J. Lu (2):
x86: Move x86 processor cache info to cpu_features
ld.so: Add --list-tunables to print tunable values
NEWS | 2 +
elf/Makefile | 8 +
elf/dl-main.h | 2 +-
elf/dl-tunables.c | 36 +++
elf/dl-tunables.h | 2 +
elf/dl-usage.c | 7 +-
elf/rtld.c | 23 ++
manual/tunables.texi | 37 +++
sysdeps/x86/cacheinfo.c | 46 ++-
sysdeps/x86/cacheinfo.h | 384 ++-----------------------
sysdeps/x86/cpu-features.c | 35 +--
sysdeps/x86/dl-cacheinfo.h | 446 +++++++++++++++++++++++++++++
sysdeps/x86/include/cpu-features.h | 22 ++
13 files changed, 652 insertions(+), 398 deletions(-)
--
2.26.2
next reply other threads:[~2020-10-17 1:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 1:02 H.J. Lu [this message]
2020-10-17 1:02 ` V3 [PATCH 1/2] x86: Move x86 processor cache info to cpu_features H.J. Lu
2020-10-17 1:02 ` V3 [PATCH 2/2] ld.so: Add --list-tunables to print tunable values H.J. Lu
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=20201017010207.6074-1-hjl.tools@gmail.com \
--to=hjl.tools@gmail.com \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).