From: Davidlohr Bueso <dave@stgolabs.net>
To: tglx@linutronix.de, pbonzini@redhat.com
Cc: bigeasy@linutronix.de, peterz@infradead.org, rostedt@goodmis.org,
torvalds@linux-foundation.org, will@kernel.org,
joel@joelfernandes.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, dave@stgolabs.net,
Davidlohr Bueso <dbueso@suse.de>
Subject: [PATCH 2/4] rcuwait: Let rcuwait_wake_up() return whether or not a task was awoken
Date: Mon, 23 Mar 2020 21:44:51 -0700 [thread overview]
Message-ID: <20200324044453.15733-3-dave@stgolabs.net> (raw)
In-Reply-To: <20200324044453.15733-1-dave@stgolabs.net>
Propagating the return value of wake_up_process() back to the caller
can come in handy for future users, such as for statistics or
accounting purposes.
Signed-off-by: Davidlohr Bueso <dbueso@suse.de>
---
include/linux/rcuwait.h | 2 +-
kernel/exit.c | 7 +++++--
2 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/include/linux/rcuwait.h b/include/linux/rcuwait.h
index 2ffe1ee6d482..6ebb23258a27 100644
--- a/include/linux/rcuwait.h
+++ b/include/linux/rcuwait.h
@@ -25,7 +25,7 @@ static inline void rcuwait_init(struct rcuwait *w)
w->task = NULL;
}
-extern void rcuwait_wake_up(struct rcuwait *w);
+extern int rcuwait_wake_up(struct rcuwait *w);
/*
* The caller is responsible for locking around rcuwait_wait_event(),
diff --git a/kernel/exit.c b/kernel/exit.c
index a33c0baffdae..dbddc9d83407 100644
--- a/kernel/exit.c
+++ b/kernel/exit.c
@@ -225,8 +225,9 @@ void release_task(struct task_struct *p)
goto repeat;
}
-void rcuwait_wake_up(struct rcuwait *w)
+int rcuwait_wake_up(struct rcuwait *w)
{
+ int ret = 0;
struct task_struct *task;
rcu_read_lock();
@@ -246,8 +247,10 @@ void rcuwait_wake_up(struct rcuwait *w)
task = rcu_dereference(w->task);
if (task)
- wake_up_process(task);
+ ret = wake_up_process(task);
rcu_read_unlock();
+
+ return ret;
}
EXPORT_SYMBOL_GPL(rcuwait_wake_up);
--
2.16.4
next prev parent reply other threads:[~2020-03-24 4:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 4:44 [PATCH -tip 0/4] kvm: Use rcuwait for vcpu blocking Davidlohr Bueso
2020-03-24 4:44 ` [PATCH 1/4] rcuwait: Fix stale wake call name in comment Davidlohr Bueso
2020-03-24 4:44 ` Davidlohr Bueso [this message]
2020-03-24 4:44 ` [PATCH 3/4] kvm: Replace vcpu->swait with rcuwait Davidlohr Bueso
2020-03-24 12:07 ` kbuild test robot
2020-03-24 16:47 ` kbuild test robot
2020-03-24 17:56 ` Davidlohr Bueso
2020-03-25 17:09 ` Paolo Bonzini
2020-04-14 21:12 ` Davidlohr Bueso
2020-04-15 12:11 ` Paolo Bonzini
2020-04-20 16:41 ` [PATCH v2] " Davidlohr Bueso
2020-04-20 17:12 ` Marc Zyngier
2020-04-20 17:25 ` Paolo Bonzini
2020-04-20 20:56 ` Davidlohr Bueso
2020-04-20 21:04 ` Paolo Bonzini
2020-04-20 21:50 ` Davidlohr Bueso
2020-04-21 9:43 ` Paolo Bonzini
2020-04-21 18:07 ` Davidlohr Bueso
2020-04-21 19:52 ` Paolo Bonzini
2020-03-24 4:44 ` [PATCH 4/4] sched/swait: Reword some of the main description Davidlohr Bueso
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=20200324044453.15733-3-dave@stgolabs.net \
--to=dave@stgolabs.net \
--cc=bigeasy@linutronix.de \
--cc=dbueso@suse.de \
--cc=joel@joelfernandes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).