From: Byungchul Park <byungchul@sk.com>
To: linux-kernel@vger.kernel.org
Cc: kernel_team@skhynix.com, torvalds@linux-foundation.org,
damien.lemoal@opensource.wdc.com, linux-ide@vger.kernel.org,
adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
mingo@redhat.com, peterz@infradead.org, will@kernel.org,
tglx@linutronix.de, rostedt@goodmis.org, joel@joelfernandes.org,
sashal@kernel.org, daniel.vetter@ffwll.ch, duyuyang@gmail.com,
johannes.berg@intel.com, tj@kernel.org, tytso@mit.edu,
willy@infradead.org, david@fromorbit.com, amir73il@gmail.com,
gregkh@linuxfoundation.org, kernel-team@lge.com,
linux-mm@kvack.org, akpm@linux-foundation.org, mhocko@kernel.org,
minchan@kernel.org, hannes@cmpxchg.org, vdavydov.dev@gmail.com,
sj@kernel.org, jglisse@redhat.com, dennis@kernel.org,
cl@linux.com, penberg@kernel.org, rientjes@google.com,
vbabka@suse.cz, ngupta@vflare.org, linux-block@vger.kernel.org,
josef@toxicpanda.com, linux-fsdevel@vger.kernel.org,
jack@suse.cz, jlayton@kernel.org, dan.j.williams@intel.com,
hch@infradead.org, djwong@kernel.org,
dri-devel@lists.freedesktop.org, rodrigosiqueiramelo@gmail.com,
melissa.srw@gmail.com, hamohammed.sa@gmail.com,
42.hyeyoo@gmail.com, chris.p.wilson@intel.com,
gwan-gyeong.mun@intel.com, max.byungchul.park@gmail.com,
boqun.feng@gmail.com, longman@redhat.com, hdanton@sina.com,
her0gyugyu@gmail.com
Subject: [PATCH v13 19/27] dept: Apply timeout consideration to waitqueue wait
Date: Wed, 6 Mar 2024 17:55:05 +0900 [thread overview]
Message-ID: <20240306085513.41482-20-byungchul@sk.com> (raw)
In-Reply-To: <20240306085513.41482-1-byungchul@sk.com>
Now that CONFIG_DEPT_AGGRESSIVE_TIMEOUT_WAIT was introduced, apply the
consideration to waitqueue wait, assuming an input 'ret' in
___wait_event() macro is used as a timeout value.
Signed-off-by: Byungchul Park <byungchul@sk.com>
---
include/linux/wait.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/wait.h b/include/linux/wait.h
index ebeb4678859f..e5e3fb2981f4 100644
--- a/include/linux/wait.h
+++ b/include/linux/wait.h
@@ -304,7 +304,7 @@ extern void init_wait_entry(struct wait_queue_entry *wq_entry, int flags);
struct wait_queue_entry __wq_entry; \
long __ret = ret; /* explicit shadow */ \
\
- sdt_might_sleep_start(NULL); \
+ sdt_might_sleep_start_timeout(NULL, __ret); \
init_wait_entry(&__wq_entry, exclusive ? WQ_FLAG_EXCLUSIVE : 0); \
for (;;) { \
long __int = prepare_to_wait_event(&wq_head, &__wq_entry, state);\
--
2.17.1
next prev parent reply other threads:[~2024-03-06 8:55 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 8:54 [PATCH v13 00/27] DEPT(Dependency Tracker) Byungchul Park
2024-03-06 8:54 ` [PATCH v13 01/27] llist: Move llist_{head,node} definition to types.h Byungchul Park
2024-03-06 8:54 ` [PATCH v13 01/27] llist: Move llist_{head, node} " Byungchul Park
2024-03-06 8:54 ` [PATCH v13 02/27] dept: Implement Dept(Dependency Tracker) Byungchul Park
2024-03-06 8:54 ` [PATCH v13 03/27] dept: Add single event dependency tracker APIs Byungchul Park
2024-03-06 8:54 ` [PATCH v13 04/27] dept: Add lock " Byungchul Park
2024-03-06 8:54 ` [PATCH v13 05/27] dept: Tie to Lockdep and IRQ tracing Byungchul Park
2024-03-06 8:54 ` [PATCH v13 06/27] dept: Add proc knobs to show stats and dependency graph Byungchul Park
2024-03-06 8:54 ` [PATCH v13 07/27] dept: Apply sdt_might_sleep_{start,end}() to wait_for_completion()/complete() Byungchul Park
2024-03-06 8:54 ` [PATCH v13 07/27] dept: Apply sdt_might_sleep_{start, end}() " Byungchul Park
2024-03-06 8:54 ` [PATCH v13 08/27] dept: Apply sdt_might_sleep_{start,end}() to swait Byungchul Park
2024-03-06 8:54 ` [PATCH v13 09/27] dept: Apply sdt_might_sleep_{start,end}() to waitqueue wait Byungchul Park
2024-03-06 8:54 ` [PATCH v13 09/27] dept: Apply sdt_might_sleep_{start, end}() " Byungchul Park
2024-03-06 8:54 ` [PATCH v13 10/27] dept: Apply sdt_might_sleep_{start, end}() to hashed-waitqueue wait Byungchul Park
2024-03-06 8:54 ` [PATCH v13 10/27] dept: Apply sdt_might_sleep_{start,end}() " Byungchul Park
2024-03-06 8:54 ` [PATCH v13 11/27] dept: Distinguish each syscall context from another Byungchul Park
2024-03-06 8:54 ` [PATCH v13 12/27] dept: Distinguish each work " Byungchul Park
2024-03-06 8:54 ` [PATCH v13 13/27] dept: Add a mechanism to refill the internal memory pools on running out Byungchul Park
2024-03-06 8:55 ` [PATCH v13 14/27] cpu/hotplug: Use a weaker annotation in AP thread Byungchul Park
2024-03-06 8:55 ` [PATCH v13 15/27] dept: Apply sdt_might_sleep_{start, end}() to dma fence wait Byungchul Park
2024-03-06 8:55 ` [PATCH v13 15/27] dept: Apply sdt_might_sleep_{start,end}() " Byungchul Park
2024-03-06 8:55 ` [PATCH v13 16/27] dept: Track timeout waits separately with a new Kconfig Byungchul Park
2024-03-06 8:55 ` [PATCH v13 17/27] dept: Apply timeout consideration to wait_for_completion()/complete() Byungchul Park
2024-03-06 8:55 ` [PATCH v13 18/27] dept: Apply timeout consideration to swait Byungchul Park
2024-03-06 8:55 ` Byungchul Park [this message]
2024-03-06 8:55 ` [PATCH v13 20/27] dept: Apply timeout consideration to hashed-waitqueue wait Byungchul Park
2024-03-06 8:55 ` [PATCH v13 21/27] dept: Apply timeout consideration to dma fence wait Byungchul Park
2024-03-06 8:55 ` [PATCH v13 22/27] dept: Record the latest one out of consecutive waits of the same class Byungchul Park
2024-03-06 8:55 ` [PATCH v13 23/27] dept: Make Dept able to work with an external wgen Byungchul Park
2024-03-06 8:55 ` [PATCH v13 24/27] dept: Track PG_locked with dept Byungchul Park
2024-03-06 8:55 ` [PATCH v13 25/27] dept: Print event context requestor's stacktrace on report Byungchul Park
2024-03-06 8:55 ` [PATCH v13 26/27] fs/jbd2: Use a weaker annotation in journal handling Byungchul Park
2024-03-06 8:55 ` [PATCH v13 27/27] dept: Add documentation for Dept Byungchul Park
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=20240306085513.41482-20-byungchul@sk.com \
--to=byungchul@sk.com \
--cc=42.hyeyoo@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=amir73il@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=chris.p.wilson@intel.com \
--cc=cl@linux.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=dan.j.williams@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=david@fromorbit.com \
--cc=dennis@kernel.org \
--cc=djwong@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=duyuyang@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=gwan-gyeong.mun@intel.com \
--cc=hamohammed.sa@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=hch@infradead.org \
--cc=hdanton@sina.com \
--cc=her0gyugyu@gmail.com \
--cc=jack@suse.cz \
--cc=jglisse@redhat.com \
--cc=jlayton@kernel.org \
--cc=joel@joelfernandes.org \
--cc=johannes.berg@intel.com \
--cc=josef@toxicpanda.com \
--cc=kernel-team@lge.com \
--cc=kernel_team@skhynix.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=longman@redhat.com \
--cc=max.byungchul.park@gmail.com \
--cc=melissa.srw@gmail.com \
--cc=mhocko@kernel.org \
--cc=minchan@kernel.org \
--cc=mingo@redhat.com \
--cc=ngupta@vflare.org \
--cc=penberg@kernel.org \
--cc=peterz@infradead.org \
--cc=rientjes@google.com \
--cc=rodrigosiqueiramelo@gmail.com \
--cc=rostedt@goodmis.org \
--cc=sashal@kernel.org \
--cc=sj@kernel.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=vbabka@suse.cz \
--cc=vdavydov.dev@gmail.com \
--cc=will@kernel.org \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.