From: Li Zefan <lizf@cn.fujitsu.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: mingo@redhat.com, hpa@zytor.com, vatsa@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, dhaval@linux.vnet.ibm.com,
balbir@in.ibm.com, akpm@linux-foundation.org, tglx@linutronix.de,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:sched/urgent] cpuset: Check if the cpus allowed is a subset of the cpuset's cpus for PF_THREAD_BOUND threads
Date: Fri, 13 Mar 2009 09:43:45 +0800 [thread overview]
Message-ID: <49B9BA51.70105@cn.fujitsu.com> (raw)
In-Reply-To: <20090313013241.GA6107@elte.hu>
CC: David Rientjes <rientjes@google.com>
Ingo Molnar wrote:
> * Dhaval Giani <dhaval@linux.vnet.ibm.com> wrote:
>
>> Commit-ID: 5a98d36112f4301f068b638d6e0db2357f7deb75
>> Gitweb: http://git.kernel.org/tip/5a98d36112f4301f068b638d6e0db2357f7deb75
>> Author: Dhaval Giani <dhaval@linux.vnet.ibm.com>
>> AuthorDate: Thu, 12 Mar 2009 23:15:01 +0530
>> Commit: Ingo Molnar <mingo@elte.hu>
>> CommitDate: Fri, 13 Mar 2009 00:21:25 +0100
>>
>> cpuset: Check if the cpus allowed is a subset of the cpuset's
>> cpus for PF_THREAD_BOUND threads
>
> Dropped this patch for now - Andrew says it got NAK-ed and he's
> handling it with other fixes.
>
It's not a bug, it's David Rientjes that introduced this behavior:
9985b0bab332289f14837eff3c6e0bcc658b58f7
And here was the discussion:
http://lkml.org/lkml/2008/6/5/310
prev parent reply other threads:[~2009-03-13 1:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 17:45 cpuset: Check if the cpus allowed is a subset of the cpuset's cpus for PF_THREAD_BOUND threads Dhaval Giani
2009-03-13 0:06 ` [tip:sched/urgent] " Dhaval Giani
2009-03-13 1:32 ` Ingo Molnar
2009-03-13 1:43 ` Li Zefan [this message]
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=49B9BA51.70105@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@in.ibm.com \
--cc=dhaval@linux.vnet.ibm.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=vatsa@linux.vnet.ibm.com \
/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