mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Kirill Tkhai <ktkhai@parallels.com>
Cc: Preeti Murthy <preeti.lkml@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@redhat.com>, Kirill Tkhai <tkhai@yandex.ru>,
	Preeti U Murthy <preeti@linux.vnet.ibm.com>
Subject: Re: [PATCH] sched: Do not stop cpu in set_cpus_allowed_ptr() if task is not running
Date: Mon, 15 Sep 2014 13:37:47 +0200	[thread overview]
Message-ID: <20140915113747.GC2840@worktop.localdomain> (raw)
In-Reply-To: <1410775350.3569.51.camel@tkhai>

On Mon, Sep 15, 2014 at 02:02:30PM +0400, Kirill Tkhai wrote:
> Hi, Preeti,
> 
> В Пн, 15/09/2014 в 15:18 +0530, Preeti Murthy пишет:
> > Hi Kirill,
> > 
> > Which tree is this patch based on? __migrate_task() does a
> > double_rq_lock/unlock() today in mainline, doesn't it? I don't
> > however see that in your patch.
> 
> it's based on recent tip tree:
> https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/
> 
> Also, once I received a build-robot message about my patch
> makes warning on allyesconfig, and since that time I learned
> about Peter's tree :) 
> 
> https://git.kernel.org/cgit/linux/kernel/git/peterz/queue.git
> 
> (This is for info, I don't know if it is right to make patches
> based on in. But really good if you was away for some time
> and you're interested in recent news without lkml archive reading.
> I use it :)

Its mostly a scratch tree to get some build coverage and to show people
what all is queued up in my quilt tree. The tree is fully recreated
every time I export my queue and at times I forget to export.

So feel free to look at, but basing work on it might not be the bestest
idea. Ideally things should find their way into -tip fairly quickly (or
get dropped on the ground if they come apart, but that usually goes
paired with an email telling you about the borkage).

  reply	other threads:[~2014-09-15 11:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-12 11:03 Kirill Tkhai
2014-09-14  9:13 ` Peter Zijlstra
2014-09-14  9:20   ` Kirill Tkhai
2014-09-14  9:55     ` Peter Zijlstra
2014-09-14  9:57       ` Kirill Tkhai
2014-09-15  9:48 ` Preeti Murthy
2014-09-15 10:02   ` Kirill Tkhai
2014-09-15 11:37     ` Peter Zijlstra [this message]
2014-09-16 11:29     ` Preeti U Murthy
2014-09-19 11:46 ` [tip:sched/core] " tip-bot for Kirill Tkhai

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=20140915113747.GC2840@worktop.localdomain \
    --to=peterz@infradead.org \
    --cc=ktkhai@parallels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=preeti.lkml@gmail.com \
    --cc=preeti@linux.vnet.ibm.com \
    --cc=tkhai@yandex.ru \
    /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

Powered by JetHome