[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080229003628.0989794e.akpm@linux-foundation.org>
Date: Fri, 29 Feb 2008 00:36:28 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Ingo Molnar <mingo@...e.hu>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Thomas Gleixner <tglx@...utronix.de>,
Oleg Nesterov <oleg@...sign.ru>,
Steven Rostedt <rostedt@...dmis.org>,
Paul Jackson <pj@....com>,
Max Krasnyanskiy <maxk@...lcomm.com>,
linux-kernel@...r.kernel.org
Subject: Re: [RFC/PATCH 0/4] CPUSET driven CPU isolation
On Fri, 29 Feb 2008 00:31:55 -0800 Andrew Morton <akpm@...ux-foundation.org> wrote:
> So I shall drop git-sched again.
And when I do this I get:
***************
*** 8125,8137 ****
return simple_read_from_buffer(buf, nbytes, ppos, tmp, len);
}
- static int cpu_rt_period_write_uint(struct cgroup *cgrp, struct cftype *cftype,
u64 rt_period_us)
{
return sched_group_set_rt_period(cgroup_tg(cgrp), rt_period_us);
}
- static u64 cpu_rt_period_read_uint(struct cgroup *cgrp, struct cftype *cft)
{
return sched_group_rt_period(cgroup_tg(cgrp));
}
--- 8125,8137 ----
return simple_read_from_buffer(buf, nbytes, ppos, tmp, len);
}
+ static int cpu_rt_period_write_u64(struct cgroup *cgrp, struct cftype *cftype,
u64 rt_period_us)
{
return sched_group_set_rt_period(cgroup_tg(cgrp), rt_period_us);
}
+ static u64 cpu_rt_period_read_u64(struct cgroup *cgrp, struct cftype *cft)
{
return sched_group_rt_period(cgroup_tg(cgrp));
}
***************
*** 8367,8374 ****
},
{
.name = "rt_period_us",
- .read_uint = cpu_rt_period_read_uint,
- .write_uint = cpu_rt_period_write_uint,
},
#endif
};
--- 8367,8374 ----
},
{
.name = "rt_period_us",
+ .read_u64 = cpu_rt_period_read_u64,
+ .write_u64 = cpu_rt_period_write_u64,
},
#endif
};
and if I then fix that up, and later restore git-sched, Paul's patch is now
broken.
Your trees continue to cause more trouble than anyone else's have ever
done, by a lot.
Let me try yesterday's git-sched.patch.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists