From: "Cao, Quanquan/曹 全全" <caoqq@fujitsu.com>
To: Dave Jiang <dave.jiang@intel.com>, vishal.l.verma@intel.com
Cc: linux-cxl@vger.kernel.org, nvdimm@lists.linux.dev
Subject: Re: [NDCTL PATCH 2/2] cxl: Add check for regions before disabling memdev
Date: Tue, 28 Nov 2023 14:35:16 +0800 [thread overview]
Message-ID: <7eaf1057-2caf-8ec9-8b79-22ad4976ef76@fujitsu.com> (raw)
In-Reply-To: <169645731012.624805.15404457479294344934.stgit@djiang5-mobl3>
> Add a check for memdev disable to see if there are active regions present
> before disabling the device. This is necessary now regions are present to
> fulfill the TODO that was left there. The best way to determine if a
> region is active is to see if there are decoders enabled for the mem
> device. This is also best effort as the state is only a snapshot the
> kernel provides and is not atomic WRT the memdev disable operation. The
> expectation is the admin issuing the command has full control of the mem
> device and there are no other agents also attempt to control the device.
>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> ---
> cxl/memdev.c | 14 ++++++++++++--
> 1 file changed, 12 insertions(+), 2 deletions(-)
>
> diff --git a/cxl/memdev.c b/cxl/memdev.c
> index f6a2d3f1fdca..314bac082719 100644
> --- a/cxl/memdev.c
> +++ b/cxl/memdev.c
> @@ -373,11 +373,21 @@ static int action_free_dpa(struct cxl_memdev *memdev,
>
> static int action_disable(struct cxl_memdev *memdev, struct action_context *actx)
> {
> + struct cxl_endpoint *ep;
> + struct cxl_port *port;
> +
> if (!cxl_memdev_is_enabled(memdev))
> return 0;
>
> - if (!param.force) {
> - /* TODO: actually detect rather than assume active */
> + ep = cxl_memdev_get_endpoint(memdev);
> + if (!ep)
> + return -ENODEV;
> +
> + port = cxl_endpoint_get_port(ep);
> + if (!port)
> + return -ENODEV;
> +
> + if (cxl_port_decoders_committed(port) && !param.force) {
> log_err(&ml, "%s is part of an active region\n",
> cxl_memdev_get_devname(memdev));
> return -EBUSY;
>
>
Hi Dave,
Based on my understanding of the logic in the "disable_region" and
"destroy_region" code, in the code logic of 'disable-region -f,' after
the check, it proceeds with the offline operation. In the code logic of
'destroy-region -f,' after the check, it performs a disable operation on
the region. For the 'disable-memdev -f' operation, after completing the
check, is it also necessary to perform corresponding operations on the
region(such as disabling region/destroying region) before disabling memdev?
next prev parent reply other threads:[~2023-11-28 6:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 22:08 [NDCTL PATCH 1/2] cxl: Save the number of decoders committed to a port Dave Jiang
2023-10-04 22:08 ` [NDCTL PATCH 2/2] cxl: Add check for regions before disabling memdev Dave Jiang
2023-11-28 6:35 ` Cao, Quanquan/曹 全全 [this message]
2023-11-28 18:13 ` Verma, Vishal L
2023-11-28 18:31 ` Alison Schofield
2023-11-28 20:23 ` Dave Jiang
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=7eaf1057-2caf-8ec9-8b79-22ad4976ef76@fujitsu.com \
--to=caoqq@fujitsu.com \
--cc=dave.jiang@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=vishal.l.verma@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