All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vikram Mulukutla <markivx@codeaurora.org>
To: rusty@rustcorp.com.au, tj@kernel.org, tglx@linutronix.de,
	akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] kthread: Atomically set completion and perform dequeue in __kthread_parkme
Date: Wed, 28 Jun 2017 07:05:38 -0700	[thread overview]
Message-ID: <2be88c3404544fff36fe0f634be78b4b@codeaurora.org> (raw)
In-Reply-To: <318fac36-66cd-7f90-df61-44042119ee2e@codeaurora.org>



Ping. This is happening on x86 across suspend/resume too.
https://bugs.freedesktop.org/show_bug.cgi?id=100113

On 2017-06-26 16:03, Vikram Mulukutla wrote:
> correcting Thomas Gleixner's email address. s/linuxtronix/linutronix
> 
> On 6/26/2017 3:18 PM, Vikram Mulukutla wrote:
>> kthread_park waits for the target kthread to park itself with
>> __kthread_parkme using a completion variable. __kthread_parkme - which 
>> is
>> invoked by the target kthread - sets the completion variable before
>> calling schedule() to voluntarily get itself off of the runqueue.

<snip>

Thanks,
Vikram

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2017-06-28 14:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26 22:18 [PATCH] kthread: Atomically set completion and perform dequeue in __kthread_parkme Vikram Mulukutla
2017-06-26 23:03 ` Vikram Mulukutla
2017-06-28 14:05   ` Vikram Mulukutla [this message]
2017-07-04 19:49   ` Thomas Gleixner
2017-07-05 17:23     ` Vikram Mulukutla
2017-07-04 16:07 ` Peter Zijlstra
2017-07-05 17:21   ` Vikram Mulukutla

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=2be88c3404544fff36fe0f634be78b4b@codeaurora.org \
    --to=markivx@codeaurora.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=stable@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.