Re: [PATCH] perf/core: fix group {cpu,task} validation

2017-08-21 Thread Peter Zijlstra
On Mon, Aug 21, 2017 at 05:01:38PM +0100, Mark Rutland wrote: > On Mon, Aug 21, 2017 at 05:53:26PM +0200, Peter Zijlstra wrote: > > On Thu, Jun 22, 2017 at 03:41:38PM +0100, Mark Rutland wrote: > > > Regardless of which events form a group, it does not make sense for the > > > events to target diff

Re: [PATCH] perf/core: fix group {cpu,task} validation

2017-08-21 Thread Mark Rutland
On Mon, Aug 21, 2017 at 05:53:26PM +0200, Peter Zijlstra wrote: > On Thu, Jun 22, 2017 at 03:41:38PM +0100, Mark Rutland wrote: > > Regardless of which events form a group, it does not make sense for the > > events to target different tasks and/or CPUs, as this leaves the group > > inconsistent and

Re: [PATCH] perf/core: fix group {cpu,task} validation

2017-08-21 Thread Peter Zijlstra
On Thu, Jun 22, 2017 at 03:41:38PM +0100, Mark Rutland wrote: > Regardless of which events form a group, it does not make sense for the > events to target different tasks and/or CPUs, as this leaves the group > inconsistent and impossible to schedule. The core perf code assumes that > these are con

Re: [PATCH] perf/core: fix group {cpu,task} validation

2017-06-23 Thread Mark Rutland
Hi, On Fri, Jun 23, 2017 at 08:56:38AM +0800, zhouchengming wrote: > On 2017/6/22 22:41, Mark Rutland wrote: > >Regardless of which events form a group, it does not make sense for the > >events to target different tasks and/or CPUs, as this leaves the group > >inconsistent and impossible to schedu

Re: [PATCH] perf/core: fix group {cpu,task} validation

2017-06-22 Thread zhouchengming
On 2017/6/22 22:41, Mark Rutland wrote: Regardless of which events form a group, it does not make sense for the events to target different tasks and/or CPUs, as this leaves the group inconsistent and impossible to schedule. The core perf code assumes that these are consistent across (successfully