From: "tip-bot2 for Peter Newman" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Peter Newman <peternewman@google.com>,
"Borislav Petkov (AMD)" <bp@alien8.de>,
Reinette Chatre <reinette.chatre@intel.com>,
Babu Moger <babu.moger@amd.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/cache] Documentation/x86: Documentation for MON group move feature
Date: Wed, 07 Jun 2023 10:52:06 -0000 [thread overview]
Message-ID: <168613512697.404.616009463445838312.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20230419125015.693566-4-peternewman@google.com>
The following commit has been merged into the x86/cache branch of tip:
Commit-ID: e0a6ede2dd884adb73a7dde80444185b655f7c79
Gitweb: https://git.kernel.org/tip/e0a6ede2dd884adb73a7dde80444185b655f7c79
Author: Peter Newman <peternewman@google.com>
AuthorDate: Wed, 19 Apr 2023 14:50:15 +02:00
Committer: Borislav Petkov (AMD) <bp@alien8.de>
CommitterDate: Wed, 07 Jun 2023 12:42:12 +02:00
Documentation/x86: Documentation for MON group move feature
Describe new support for moving MON groups to a new parent CTRL_MON
group and its restrictions.
Signed-off-by: Peter Newman <peternewman@google.com>
Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Tested-by: Babu Moger <babu.moger@amd.com>
Link: https://lore.kernel.org/r/20230419125015.693566-4-peternewman@google.com
---
Documentation/arch/x86/resctrl.rst | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Documentation/arch/x86/resctrl.rst b/Documentation/arch/x86/resctrl.rst
index 387ccbc..cb05d90 100644
--- a/Documentation/arch/x86/resctrl.rst
+++ b/Documentation/arch/x86/resctrl.rst
@@ -287,6 +287,13 @@ Removing a directory will move all tasks and cpus owned by the group it
represents to the parent. Removing one of the created CTRL_MON groups
will automatically remove all MON groups below it.
+Moving MON group directories to a new parent CTRL_MON group is supported
+for the purpose of changing the resource allocations of a MON group
+without impacting its monitoring data or assigned tasks. This operation
+is not allowed for MON groups which monitor CPUs. No other move
+operation is currently allowed other than simply renaming a CTRL_MON or
+MON group.
+
All groups contain the following files:
"tasks":
next prev parent reply other threads:[~2023-06-07 10:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 12:50 [PATCH v6 0/3] x86/resctrl: Implement rename to help move containers' tasks Peter Newman
2023-04-19 12:50 ` [PATCH v6 1/3] x86/resctrl: Factor rdtgroup lock for multi-file ops Peter Newman
2023-06-07 10:52 ` [tip: x86/cache] " tip-bot2 for Peter Newman
2023-04-19 12:50 ` [PATCH v6 2/3] x86/resctrl: Implement rename op for mon groups Peter Newman
2023-06-07 10:52 ` [tip: x86/cache] " tip-bot2 for Peter Newman
2023-04-19 12:50 ` [PATCH v6 3/3] Documentation/x86: Documentation for MON group move feature Peter Newman
2023-06-07 10:52 ` tip-bot2 for Peter Newman [this message]
2023-05-03 14:50 ` [PATCH v6 0/3] x86/resctrl: Implement rename to help move containers' tasks Moger, Babu
2023-06-01 21:38 ` Reinette Chatre
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=168613512697.404.616009463445838312.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peternewman@google.com \
--cc=reinette.chatre@intel.com \
--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
all inboxes | Powered by JetHome®