From: Chen Yu <yu.c.chen@intel.com>
To: x86@kernel.org
Cc: Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Will Deacon <will@kernel.org>, Fenghua Yu <fenghua.yu@intel.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Tony Luck <tony.luck@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
Michal Hocko <mhocko@suse.com>, Kees Cook <keescook@chromium.org>,
Christian Brauner <christian@brauner.io>,
Shakeel Butt <shakeelb@google.com>,
Casey Schaufler <casey@schaufler-ca.com>,
Konstantin Khlebnikov <khlebnikov@yandex-team.ru>,
Kent Overstreet <kent.overstreet@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Chen Yu <yu.c.chen@intel.com>
Subject: [PATCH 1/2][v2] resctrl: Add CPU_RESCTRL
Date: Fri, 15 Nov 2019 13:24:20 +0800 [thread overview]
Message-ID: <a39663fd4ce167e65b6d41027c3433dc00bf54f0.1573788882.git.yu.c.chen@intel.com> (raw)
In-Reply-To: <cover.1573788882.git.yu.c.chen@intel.com>
Introduce a generic option called CPU_RESCTRL which
is selected by the arch-specific ones CONFIG_X86_RESCTRL
or CONFIG_ARM64_RESCTRL in the future. The generic one will
cover the resctrl filesystem and other generic and shared
bits of functionality.
Suggested-by: Borislav Petkov <bp@suse.de>
Signed-off-by: Chen Yu <yu.c.chen@intel.com>
---
arch/Kconfig | 4 ++++
arch/x86/Kconfig | 1 +
2 files changed, 5 insertions(+)
diff --git a/arch/Kconfig b/arch/Kconfig
index 5f8a5d84dbbe..3886cf0052a8 100644
--- a/arch/Kconfig
+++ b/arch/Kconfig
@@ -960,6 +960,10 @@ config RELR
config ARCH_HAS_MEM_ENCRYPT
bool
+config CPU_RESCTRL
+ bool
+ def_bool n
+
source "kernel/gcov/Kconfig"
source "scripts/gcc-plugins/Kconfig"
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 8ef85139553f..a8a12493e8c2 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -455,6 +455,7 @@ config X86_CPU_RESCTRL
bool "x86 CPU resource control support"
depends on X86 && (CPU_SUP_INTEL || CPU_SUP_AMD)
select KERNFS
+ select CPU_RESCTRL
help
Enable x86 CPU resource control support.
--
2.17.1
next prev parent reply other threads:[~2019-11-15 5:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 5:23 [PATCH 0/2][v2] Add task resctrl information in procfs Chen Yu
2019-11-15 5:24 ` Chen Yu [this message]
2019-11-15 8:46 ` [PATCH 1/2][v2] resctrl: Add CPU_RESCTRL Borislav Petkov
2019-11-15 5:25 ` [PATCH 2/2][v2] x86/resctrl: Add task resctrl information display Chen Yu
2019-11-15 9:24 ` Borislav Petkov
2019-11-16 15:01 ` Ryan Chen
2019-11-18 14:48 ` Borislav Petkov
2019-11-20 7:54 ` Yu Chen
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=a39663fd4ce167e65b6d41027c3433dc00bf54f0.1573788882.git.yu.c.chen@intel.com \
--to=yu.c.chen@intel.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=casey@schaufler-ca.com \
--cc=christian@brauner.io \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=kent.overstreet@gmail.com \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=reinette.chatre@intel.com \
--cc=shakeelb@google.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=will@kernel.org \
--cc=x86@kernel.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).