From: "Huang, Kai" <kai.huang@intel.com>
To: "chenridong@huawei.com" <chenridong@huawei.com>,
"linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
"cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
"mkoutny@suse.com" <mkoutny@suse.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"haitao.huang@linux.intel.com" <haitao.huang@linux.intel.com>,
"tim.c.chen@linux.intel.com" <tim.c.chen@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"tj@kernel.org" <tj@kernel.org>,
"jarkko@kernel.org" <jarkko@kernel.org>,
"Mehta, Sohil" <sohil.mehta@intel.com>,
"hpa@zytor.com" <hpa@zytor.com>, "bp@alien8.de" <bp@alien8.de>,
"x86@kernel.org" <x86@kernel.org>
Cc: "mikko.ylinen@linux.intel.com" <mikko.ylinen@linux.intel.com>,
"seanjc@google.com" <seanjc@google.com>,
"anakrish@microsoft.com" <anakrish@microsoft.com>,
"Zhang, Bo" <zhanb@microsoft.com>,
"kristen@linux.intel.com" <kristen@linux.intel.com>,
"yangjie@microsoft.com" <yangjie@microsoft.com>,
"Li, Zhiquan1" <zhiquan1.li@intel.com>,
"chrisyan@microsoft.com" <chrisyan@microsoft.com>
Subject: Re: [PATCH v17 02/16] cgroup/misc: Add per resource callbacks for CSS events
Date: Mon, 2 Sep 2024 09:43:21 +0000 [thread overview]
Message-ID: <1fe27f4dfbfbdc887458df88b2ebedc9cbd2d566.camel@intel.com> (raw)
In-Reply-To: <20240830164038.39343-3-haitao.huang@linux.intel.com>
On Fri, 2024-08-30 at 09:40 -0700, Haitao Huang wrote:
> From: Kristen Carlson Accardi <kristen@linux.intel.com>
>
> The misc cgroup controller (subsystem) currently does not perform
> resource type specific action for Cgroups Subsystem State (CSS) events:
> the 'css_alloc' event when a cgroup is created and the 'css_free' event
> when a cgroup is destroyed.
>
> Define callbacks for those events and allow resource providers to
> register the callbacks per resource type as needed. This will be
> utilized later by the EPC misc cgroup support implemented in the SGX
> driver.
>
> The SGX callbacks will need to access the 'struct misc_cg'. Pass
> 'struct misc_cg' to the callbacks but not the 'struct misc_res' because
> the latter doesn't have a pointer pointing back to 'struct misc_cg'.
>
> Link: https://lore.kernel.org/lkml/op.2kdw36otwjvjmi@hhuan26-mobl.amr.corp.intel.com/
>
> Signed-off-by: Kristen Carlson Accardi <kristen@linux.intel.com>
> Co-developed-by: Haitao Huang <haitao.huang@linux.intel.com>
> Signed-off-by: Haitao Huang <haitao.huang@linux.intel.com>
> Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
> Reviewed-by: Tejun Heo <tj@kernel.org>
> Tested-by: Jarkko Sakkinen <jarkko@kernel.org>
> ---
>
Acked-by: Kai Huang <kai.huang@intel.com>
next prev parent reply other threads:[~2024-09-02 11:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 16:40 [PATCH v17 00/16] Add Cgroup support for SGX EPC memory Haitao Huang
2024-08-30 16:40 ` [PATCH v17 01/16] x86/sgx: Replace boolean parameters with enums Haitao Huang
2024-08-30 16:40 ` [PATCH v17 02/16] cgroup/misc: Add per resource callbacks for CSS events Haitao Huang
2024-09-02 9:43 ` Huang, Kai [this message]
2024-08-30 16:40 ` [PATCH v17 03/16] cgroup/misc: Expose APIs for SGX driver Haitao Huang
2024-08-30 16:40 ` [PATCH v17 04/16] cgroup/misc: Add SGX EPC resource type Haitao Huang
2024-08-30 16:40 ` [PATCH v17 05/16] x86/sgx: Implement basic EPC misc cgroup functionality Haitao Huang
2024-08-30 16:40 ` [PATCH v17 06/16] x86/sgx: Add sgx_epc_lru_list to encapsulate LRU list Haitao Huang
2024-08-30 16:40 ` [PATCH v17 07/16] x86/sgx: Abstract tracking reclaimable pages in LRU Haitao Huang
2024-08-30 16:40 ` [PATCH v17 08/16] x86/sgx: Encapsulate uses of the global LRU Haitao Huang
2024-08-30 16:40 ` [PATCH v17 09/16] x86/sgx: Add basic EPC reclamation flow for cgroup Haitao Huang
2024-08-30 16:40 ` [PATCH v17 10/16] x86/sgx: Implement async reclamation " Haitao Huang
2024-08-30 16:40 ` [PATCH v17 11/16] x86/sgx: Charge mem_cgroup for per-cgroup reclamation Haitao Huang
2024-08-30 16:40 ` [PATCH v17 12/16] x86/sgx: Implement direct reclamation for cgroups Haitao Huang
2024-08-30 16:40 ` [PATCH v17 13/16] x86/sgx: Revise global reclamation for EPC cgroups Haitao Huang
2024-08-30 16:40 ` [PATCH v17 14/16] x86/sgx: Turn on per-cgroup EPC reclamation Haitao Huang
2024-08-30 16:40 ` [PATCH v17 15/16] Docs/x86/sgx: Add description for cgroup support Haitao Huang
2024-08-30 16:40 ` [PATCH v17 16/16] selftests/sgx: Add scripts for EPC cgroup testing Haitao Huang
[not found] ` <FR4P281MB364378DFE998FADC1CE8B615DF1C2@FR4P281MB3643.DEUP281.PROD.OUTLOOK.COM>
2025-01-15 20:16 ` [PATCH v17 00/16] Add Cgroup support for SGX EPC memory Jarkko Sakkinen
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=1fe27f4dfbfbdc887458df88b2ebedc9cbd2d566.camel@intel.com \
--to=kai.huang@intel.com \
--cc=anakrish@microsoft.com \
--cc=bp@alien8.de \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huawei.com \
--cc=chrisyan@microsoft.com \
--cc=dave.hansen@linux.intel.com \
--cc=haitao.huang@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jarkko@kernel.org \
--cc=kristen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mikko.ylinen@linux.intel.com \
--cc=mingo@redhat.com \
--cc=mkoutny@suse.com \
--cc=seanjc@google.com \
--cc=sohil.mehta@intel.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=tj@kernel.org \
--cc=x86@kernel.org \
--cc=yangjie@microsoft.com \
--cc=zhanb@microsoft.com \
--cc=zhiquan1.li@intel.com \
/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