From: Marc Herbert <Marc.Herbert@linux.intel.com>
To: Shiyang Ruan <ruansy.fnst@fujitsu.com>,
Dan Williams <dan.j.williams@intel.com>
Cc: vishal.l.verma@intel.com, sunfishho12@gmail.com,
linux-cxl@vger.kernel.org
Subject: Re: [PATCH] test/cxl-xor-region.sh: remove redundant waitting
Date: Mon, 19 May 2025 22:26:53 -0700 [thread overview]
Message-ID: <f5ed30fa-e19a-43a0-9067-2562080ddbab@linux.intel.com> (raw)
In-Reply-To: <859d8415-5822-4f14-a911-1f1e48e344fe@fujitsu.com>
On 2025-05-19 20:38, Shiyang Ruan wrote:
>
> Yes, I have tried to use `systemd-run my-original-script.sh` to
> achieve my goal. It creates a new process which is outside of udev
> queue so it won't cause the deadlock.
Thanks for confirming! Also, I didn't know about systemd-run, it looks
very useful. Thanks for sharing. run_qemu.sh should probably use it; it
would simplify things.
Learning about systemd is a lifelong process...
> BTW, after you talked with Dan, do you think it is still necessary to
> add the `--no-wait` parameter to avoid waiting for the udev queue
> empty in some specific scenarios?
Dan's recommendation to have two different "modes" still makes sense to
me.
> Do you have any plans to implement this feature?
I'm not aware of anyone who volunteered to do this yet. I bet
there will be reviewers if someone does.
next prev parent reply other threads:[~2025-05-20 5:27 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
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 [this message]
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=f5ed30fa-e19a-43a0-9067-2562080ddbab@linux.intel.com \
--to=marc.herbert@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-cxl@vger.kernel.org \
--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