From: Alison Schofield <alison.schofield@intel.com>
To: ruansy.fnst <ruansy.fnst@fujitsu.com>
Cc: <linux-cxl@vger.kernel.org>, <dan.j.williams@intel.com>,
<vishal.l.verma@intel.com>, <sunfishho12@gmail.com>,
<nvdimm@lists.linux.dev>
Subject: Re: [PATCH] test/cxl-xor-region.sh: remove redundant waitting
Date: Fri, 16 May 2025 14:36:51 -0700 [thread overview]
Message-ID: <aCev83lpHZlsYV1d@aschofie-mobl2.lan> (raw)
In-Reply-To: <20250514112003.2150272-1-ruansy.fnst@fujitsu.com>
On Wed, May 14, 2025 at 07:20:03PM +0800, ruansy.fnst wrote:
> From: Ruan Shiyang <ruansy.fnst@fujitsu.com>
>
> Now that cxl_wait_probe() has been added[1] to wait for udev queue
> empty, the `udevadm settle` here is no longer necessary.
>
> [1] b231603 cxl/lib: Add cxl_wait_probe()
>
> Signed-off-by: Ruan Shiyang <ruansy.fnst@fujitsu.com>
Reviewed-by: Alison Schofield <alison.schofield@intel.com>
Hi Ruan, It looks like I snuck this one in right before Dan introduced
udevadm settle and cleaned up all the usages. I'll take this patch as
is. The next time you patch ndctl, do these:
[PATCH] --> [ndctl PATCH]
Send to nvdimm@lists.linux.dev and 'cc linux-cxl@vger.kernel.org
if it's CXL related like this one.
I suggest you resend this udev question in a new email to linux-cxl
list to draw attention.
Thanks for the patch!
>
> ===
> Question to Dan:
>
> I understand how cxl_wait_probe() work, but I have some questions about
> the motivation of adding this function: Firstly, is it function added
> for simply waiting for new added CXL device been ready before cxl
> command does the actual work? Just for replacing `udevadm settle`'s
> work?
>
> Now I am facing a problem that cxl command takes a long time to complete
> when I run it in a udev rule(do some configuration when CXL memdev is
> added). I found it is caused by this function: waitting for udev
> queue's endding but itself is in the queue. The cxl_wait_probe()
> function does not seem to allow me to do that. So, the 2nd question is:
> is it against the spec to run cxl command in a udev rule?
> ====
> ---
> test/cxl-xor-region.sh | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/test/cxl-xor-region.sh b/test/cxl-xor-region.sh
> index b9e1d79..fb4f9a0 100644
> --- a/test/cxl-xor-region.sh
> +++ b/test/cxl-xor-region.sh
> @@ -14,7 +14,6 @@ check_prereq "jq"
>
> modprobe -r cxl_test
> modprobe cxl_test interleave_arithmetic=1
> -udevadm settle
> rc=1
>
> # THEORY OF OPERATION: Create x1,2,3,4 regions to exercise the XOR math
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2025-05-16 21:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 11:20 [PATCH] test/cxl-xor-region.sh: remove redundant waitting ruansy.fnst
2025-05-16 21:36 ` Alison Schofield [this message]
2025-05-20 3:54 ` Shiyang Ruan
2025-05-16 23:50 ` cxl <-> udev deadlock? Marc Herbert
2025-05-17 0:23 ` [PATCH] test/cxl-xor-region.sh: remove redundant waitting dan.j.williams
2025-05-19 21:47 ` Marc Herbert
2025-05-19 23:09 ` Dan Williams
2025-05-20 1:00 ` Marc Herbert
2025-05-20 3:38 ` Shiyang Ruan
2025-05-20 5:26 ` Marc Herbert
2025-05-28 20:49 ` Alison Schofield
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=aCev83lpHZlsYV1d@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=ruansy.fnst@fujitsu.com \
--cc=sunfishho12@gmail.com \
--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