mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: David Kershner <david.kershner@unisys.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Tejun Heo <tj@kernel.org>,
	laijs@cn.fujitsu.com, nacc@linux.vnet.ibm.com,
	nhorman@redhat.com, Ingo Molnar <mingo@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	jes.sorensen@redhat.com, sparmaintainer@unisys.com
Subject: Re: [PATCH] kthread: Export kthread functions
Date: Sun, 26 Jul 2015 10:46:37 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.11.1507261042570.18576@nanos> (raw)
In-Reply-To: <CAFLxGvw3LEWc5=85OrSM4DK6fUma5uPaRK+RpzHBs4DBcM+fEg@mail.gmail.com>

On Sat, 25 Jul 2015, Richard Weinberger wrote:

> On Sat, Jul 25, 2015 at 12:45 AM, David Kershner
> <david.kershner@unisys.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

  parent reply	other threads:[~2015-07-26  8:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24 22:45 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 [this message]
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 ` [PATCH v2] " David Kershner
2015-07-28 21:27   ` 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=alpine.DEB.2.11.1507261042570.18576@nanos \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=david.kershner@unisys.com \
    --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=richard.weinberger@gmail.com \
    --cc=sparmaintainer@unisys.com \
    --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®