Re: [PATCH v2] sched: introduce sched_switch_post trace event

2015-07-08 Thread Cong Wang
On Mon, Jul 6, 2015 at 11:45 PM, Peter Zijlstra wrote: > On Mon, Jul 06, 2015 at 12:15:45PM -0700, Cong Wang wrote: >> Currently we only have one sched_switch trace event >> for task switching, which is generated very early during >> task switch. When we try to monitor per-container perf >> events

Re: [PATCH v2] sched: introduce sched_switch_post trace event

2015-07-08 Thread Cong Wang
On Mon, Jul 6, 2015 at 5:15 PM, Steven Rostedt wrote: > On Mon, 6 Jul 2015 12:15:45 -0700 > Cong Wang wrote: > >> Currently we only have one sched_switch trace event >> for task switching, which is generated very early during >> task switch. When we try to monitor per-container perf >> events, t

Re: [PATCH v2] sched: introduce sched_switch_post trace event

2015-07-06 Thread Peter Zijlstra
On Mon, Jul 06, 2015 at 12:15:45PM -0700, Cong Wang wrote: > Currently we only have one sched_switch trace event > for task switching, which is generated very early during > task switch. When we try to monitor per-container perf > events, this is not what we expect. > > For example, we have a proc

Re: [PATCH v2] sched: introduce sched_switch_post trace event

2015-07-06 Thread Steven Rostedt
On Mon, 6 Jul 2015 12:15:45 -0700 Cong Wang wrote: > Currently we only have one sched_switch trace event > for task switching, which is generated very early during > task switch. When we try to monitor per-container perf > events, this is not what we expect. > > For example, we have a process A

[PATCH v2] sched: introduce sched_switch_post trace event

2015-07-06 Thread Cong Wang
Currently we only have one sched_switch trace event for task switching, which is generated very early during task switch. When we try to monitor per-container perf events, this is not what we expect. For example, we have a process A which is in the cgroup we monitor, and process B which isn't, whe