On Thu, Apr 25, 2013 at 09:34:37AM +0200, Ingo Molnar wrote:
>
> * Andrew Morton <a...@linux-foundation.org> wrote:
>
> > On Thu, 25 Apr 2013 08:57:04 +0200 Ingo Molnar <mi...@kernel.org> wrote:
> >
> > > > PF_THREAD_BOUND was removed/replaced in linux-next's a9ab775bc
> > > > ("workqueue: directly restore CPU affinity of workers from CPU_ONLINE")
> > >
> > > I don't see PF_THREAD_BOUND being removed by commit a9ab775bc. Did you
> > > mean some other commit?
> >
> > commit 14a40ffccd6163bbcd1d6f32b28a88ffe6149fc6
> > Author: Tejun Heo <t...@kernel.org>
> > Date: Tue Mar 19 13:45:20 2013 -0700
> >
> > sched: replace PF_THREAD_BOUND with PF_NO_SETAFFINITY
>
> I don't think much action is needed: whenever someone integrates the
> workqueue tree with these reboot changes, or the workqueue changes hit
> upstream, a s/PF_THREAD_BOUND/PF_NO_SETAFFINITY should do the trick,
> right?
>
> Btw., if that's true then the workqueue tree should probably grow this
> helper:
>
> #define PF_THREAD_BOUND PF_NO_SETAFFINITY
Andrew, how about I add:
--- a/kernel/reboot.c
+++ b/kernel/reboot.c
@@ -155,6 +155,9 @@ static int __init reboot_setup(char *str)
}
__setup("reboot=", reboot_setup);
+#ifndef PF_THREAD_BOUND
+#define PF_THREAD_BOUND PF_NO_SETAFFINITY
+#endif
static void migrate_to_reboot_cpu(void)
{
to this patch and then add another patch to the series to remove those.
That will make the stable pull more clear and accomplish the same final
outcome.
Thanks,
Robin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
