[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1507261042570.18576@nanos>
Date: Sun, 26 Jul 2015 10:46:37 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Richard Weinberger <richard.weinberger@...il.com>
cc: David Kershner <david.kershner@...sys.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Tejun Heo <tj@...nel.org>, laijs@...fujitsu.com,
nacc@...ux.vnet.ibm.com, nhorman@...hat.com,
Ingo Molnar <mingo@...hat.com>,
LKML <linux-kernel@...r.kernel.org>, jes.sorensen@...hat.com,
sparmaintainer@...sys.com
Subject: Re: [PATCH] kthread: Export kthread functions
On Sat, 25 Jul 2015, Richard Weinberger wrote:
> On Sat, Jul 25, 2015 at 12:45 AM, David Kershner
> <david.kershner@...sys.com> 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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists