linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@canonical.com>
To: Colin Cross <ccross@google.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	"open list:GENERIC INCLUDE/A..." <linux-arch@vger.kernel.org>,
	"linaro-mm-sig@lists.linaro.org" <linaro-mm-sig@lists.linaro.org>,
	robdclark@gmail.com,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	daniel@ffwll.ch, Sumit Semwal <sumit.semwal@linaro.org>,
	linux-media@vger.kernel.org
Subject: Re: [PATCH 1/7] sched: allow try_to_wake_up to be used internally outside of core.c
Date: Tue, 14 Jan 2014 09:35:06 +0100	[thread overview]
Message-ID: <52D4F6BA.9010802@canonical.com> (raw)
In-Reply-To: <CAMbhsRTBSzAsBke0H4cwJMUe4449KbD6cvyLuNV4ijx0L+czFw@mail.gmail.com>

op 13-01-14 19:50, Colin Cross schreef:
> On Mon, Jan 13, 2014 at 4:31 AM, Maarten Lankhorst
> <maarten.lankhorst@canonical.com> wrote:
>> The kernel fence implementation doesn't use event queues, but needs
>> to perform the same wake up. The symbol is not exported, since the
>> fence implementation is not built as a module.
>>
>> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@canonical.com>
>> ---
>>  include/linux/wait.h |    1 +
>>  kernel/sched/core.c  |    2 +-
>>  2 files changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/include/linux/wait.h b/include/linux/wait.h
>> index eaa00b10abaa..c54e3ef50134 100644
>> --- a/include/linux/wait.h
>> +++ b/include/linux/wait.h
>> @@ -12,6 +12,7 @@
>>  typedef struct __wait_queue wait_queue_t;
>>  typedef int (*wait_queue_func_t)(wait_queue_t *wait, unsigned mode, int flags, void *key);
>>  int default_wake_function(wait_queue_t *wait, unsigned mode, int flags, void *key);
>> +int try_to_wake_up(struct task_struct *p, unsigned int state, int wake_flags);
>>
>>  struct __wait_queue {
>>         unsigned int            flags;
>> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
>> index a88f4a485c5e..f41d317042dd 100644
>> --- a/kernel/sched/core.c
>> +++ b/kernel/sched/core.c
>> @@ -1578,7 +1578,7 @@ static void ttwu_queue(struct task_struct *p, int cpu)
>>   * Return: %true if @p was woken up, %false if it was already running.
>>   * or @state didn't match @p's state.
>>   */
>> -static int
>> +int
>>  try_to_wake_up(struct task_struct *p, unsigned int state, int wake_flags)
>>  {
>>         unsigned long flags;
>>
> wake_up_state is already available in linux/sched.h, can you use that?
>
Indeed! Thanks for the catch.

~Maarten

  reply	other threads:[~2014-01-14  8:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 12:31 [PATCH 0/7] dma-buf synchronization patches Maarten Lankhorst
2014-01-13 12:31 ` Maarten Lankhorst
2014-01-13 12:31 ` [PATCH 1/7] sched: allow try_to_wake_up to be used internally outside of core.c Maarten Lankhorst
2014-01-13 12:31   ` Maarten Lankhorst
2014-01-13 18:50   ` Colin Cross
2014-01-14  8:35     ` Maarten Lankhorst [this message]
2014-01-13 12:31 ` [PATCH 2/7] fence: dma-buf cross-device synchronization (v16) Maarten Lankhorst
2014-01-13 12:31   ` Maarten Lankhorst
2014-01-13 12:32 ` [PATCH 3/7] seqno-fence: Hardware dma-buf implementation of fencing (v4) Maarten Lankhorst
2014-01-13 12:32   ` Maarten Lankhorst
2014-01-13 12:32 ` [PATCH 4/7] dma-buf: use reservation objects Maarten Lankhorst
2014-01-13 12:32   ` Maarten Lankhorst
2014-01-15 17:03   ` Mauro Carvalho Chehab
2014-01-13 12:32 ` [PATCH 5/7] android: convert sync to fence api, v3 Maarten Lankhorst
2014-01-13 12:32   ` Maarten Lankhorst
2014-01-13 12:32 ` [PATCH 6/7] reservation: add support for fences to enable cross-device synchronisation Maarten Lankhorst
2014-01-13 12:32   ` Maarten Lankhorst
2014-01-13 12:33 ` [PATCH 7/7] dma-buf: add poll support Maarten Lankhorst
2014-01-13 12:33   ` Maarten Lankhorst

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=52D4F6BA.9010802@canonical.com \
    --to=maarten.lankhorst@canonical.com \
    --cc=ccross@google.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=robdclark@gmail.com \
    --cc=sumit.semwal@linaro.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;
as well as URLs for NNTP newsgroup(s).