Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755033AbbGZIrF (ORCPT ); Sun, 26 Jul 2015 04:47:05 -0400 Received: from www.linutronix.de ([62.245.132.108]:52960 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752942AbbGZIrC (ORCPT ); Sun, 26 Jul 2015 04:47:02 -0400 Date: Sun, 26 Jul 2015 10:46:37 +0200 (CEST) From: Thomas Gleixner To: Richard Weinberger cc: David Kershner , Andrew Morton , Tejun Heo , laijs@cn.fujitsu.com, nacc@linux.vnet.ibm.com, nhorman@redhat.com, Ingo Molnar , LKML , jes.sorensen@redhat.com, sparmaintainer@unisys.com Subject: Re: [PATCH] kthread: Export kthread functions In-Reply-To: Message-ID: References: <1437777920-31156-1-git-send-email-david.kershner@unisys.com> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1388 Lines: 36 On Sat, 25 Jul 2015, Richard Weinberger wrote: > On Sat, Jul 25, 2015 at 12:45 AM, David Kershner > wrote: > > 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. > > Are you sure that you need these function? > You would be the first user. And a reasonable one. The use case is sensible and it's preferrable that people reuse known to work core facilities instead of creating their own variants. > Please see: https://lkml.org/lkml/2015/7/8/1150 Please do not use lkml.org links. lkml.org sucks. Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/