From: Andi Kleen <ak@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] [PATCH 0/1] SMTCTL 0
Date: Thu, 7 Jun 2018 13:54:54 -0700 [thread overview]
Message-ID: <cover.1528404649.git.ak@linux.intel.com> (raw)
Here's an alternative proposal for SMT disabling.
I reimplemented my script as a C tool and put it into tools/*
# smtctl --enable
# smtctl --disable
# smtctl --print
Advantages:
- No kernel changes (although it would benefit from a minor one,
see the commit)
- Much easier to use at runtime than opaque sysfs
- Encourages the right use model of only switching SMT state
when it is actually needed and based on a conscious decision,
not unnecessarily or globally.
Andi Kleen (1):
tools/smtctl: Add smtctl to enable/disable SMT at runtime
tools/smtctl/Makefile | 10 ++
tools/smtctl/smtctl.c | 257 ++++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 267 insertions(+)
create mode 100644 tools/smtctl/Makefile
create mode 100644 tools/smtctl/smtctl.c
--
2.14.3
next reply other threads:[~2018-06-07 20:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 20:54 Andi Kleen [this message]
2018-06-07 20:54 ` [MODERATED] [PATCH 1/1] SMTCTL 1 Andi Kleen
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=cover.1528404649.git.ak@linux.intel.com \
--to=ak@linux.intel.com \
--cc=speck@linutronix.de \
/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).