From: David Kershner <david.kershner@unisys.com>
To: <akpm@linux-foundation.org>
Cc: <tj@kernel.org>, <laijs@cn.fujitsu.com>,
<nacc@linux.vnet.ibm.com>, <nhorman@redhat.com>,
<tglx@linutronix.de>, <mingo@redhat.com>,
<linux-kernel@vger.kernel.org>, <jes.sorensen@redhat.com>,
<sparmaintainer@unisys.com>,
David Kershner <david.kershner@unisys.com>
Subject: [PATCH v2] kthread: Export kthread functions
Date: Tue, 28 Jul 2015 11:59:01 -0400 [thread overview]
Message-ID: <1438099141-8614-1-git-send-email-david.kershner@unisys.com> (raw)
In-Reply-To: <1437777920-31156-1-git-send-email-david.kershner@unisys.com>
The s-Par visornic driver, currently in staging, processes a queue
being serviced by the an s-Par service partition. We can get a message
that something has happened with the Service Partition, when that
happens, we must not access the channel until we get a message that the
service partition is back again.
The visornic driver has a thread for processing the channel, when we
get the message, we need to be able to park the thread and then resume
it when the problem clears.
We can do this with kthread_park and unpark but they are not exported
from the kernel, this patch exports the needed functions.
Signed-off-by: David Kershner <david.kershner@unisys.com>
---
kernel/kthread.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/kernel/kthread.c b/kernel/kthread.c
index 10e489c..fdea0be 100644
--- a/kernel/kthread.c
+++ b/kernel/kthread.c
@@ -97,6 +97,7 @@ bool kthread_should_park(void)
{
return test_bit(KTHREAD_SHOULD_PARK, &to_kthread(current)->flags);
}
+EXPORT_SYMBOL_GPL(kthread_should_park);
/**
* kthread_freezable_should_stop - should this freezable kthread return now?
@@ -171,6 +172,7 @@ void kthread_parkme(void)
{
__kthread_parkme(to_kthread(current));
}
+EXPORT_SYMBOL_GPL(kthread_parkme);
static int kthread(void *_create)
{
@@ -411,6 +413,7 @@ void kthread_unpark(struct task_struct *k)
if (kthread)
__kthread_unpark(k, kthread);
}
+EXPORT_SYMBOL_GPL(kthread_unpark);
/**
* kthread_park - park a thread created by kthread_create().
@@ -441,6 +444,7 @@ int kthread_park(struct task_struct *k)
}
return ret;
}
+EXPORT_SYMBOL_GPL(kthread_park);
/**
* kthread_stop - stop a thread created by kthread_create().
--
1.9.1
next prev parent reply other threads:[~2015-07-28 16:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 22:45 [PATCH] " David Kershner
2015-07-24 23:14 ` Neil Horman
2015-07-25 12:05 ` Richard Weinberger
2015-07-26 0:50 ` Kershner, David A
2015-07-26 8:46 ` Thomas Gleixner
2015-07-27 15:45 ` Ingo Molnar
2015-07-27 15:49 ` Neil Horman
2015-07-27 16:01 ` Kershner, David A
2015-07-28 15:59 ` David Kershner [this message]
2015-07-28 21:27 ` [PATCH v2] " Andrew Morton
2015-07-29 10:34 ` Thomas Gleixner
2015-07-30 3:48 ` yalin wang
2015-07-30 12:02 ` Neil Horman
2015-07-31 4:16 ` yalin wang
2015-07-31 8:19 ` Thomas Gleixner
2015-07-31 14:14 ` Thomas Gleixner
2015-08-01 7:12 ` yalin wang
2015-08-01 7:20 ` Thomas Gleixner
2015-08-01 13:32 ` Neil Horman
2015-08-03 2:23 ` yalin wang
2015-08-03 2:42 ` Jes Sorensen
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=1438099141-8614-1-git-send-email-david.kershner@unisys.com \
--to=david.kershner@unisys.com \
--cc=akpm@linux-foundation.org \
--cc=jes.sorensen@redhat.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nacc@linux.vnet.ibm.com \
--cc=nhorman@redhat.com \
--cc=sparmaintainer@unisys.com \
--cc=tglx@linutronix.de \
--cc=tj@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
all inboxes | Powered by JetHome®