On Tue, Feb 25, 2014 at 11:38:48AM +, Peter Zijlstra wrote:
> On Mon, Feb 10, 2014 at 05:44:20PM +, Mark Rutland wrote:
> > Currently perf_event_context::type is used to determine whether a
> > context is cpu-bound or task-bound. However perf_event_context::task can
> > be used to
On Tue, Feb 25, 2014 at 11:38:48AM +, Peter Zijlstra wrote:
On Mon, Feb 10, 2014 at 05:44:20PM +, Mark Rutland wrote:
Currently perf_event_context::type is used to determine whether a
context is cpu-bound or task-bound. However perf_event_context::task can
be used to determine this
On Mon, Feb 10, 2014 at 05:44:20PM +, Mark Rutland wrote:
> Currently perf_event_context::type is used to determine whether a
> context is cpu-bound or task-bound. However perf_event_context::task can
> be used to determine this just as cheaply, and requires no additional
> initialisation.
>
On Mon, Feb 10, 2014 at 05:44:20PM +, Mark Rutland wrote:
Currently perf_event_context::type is used to determine whether a
context is cpu-bound or task-bound. However perf_event_context::task can
be used to determine this just as cheaply, and requires no additional
initialisation.
This
Currently perf_event_context::type is used to determine whether a
context is cpu-bound or task-bound. However perf_event_context::task can
be used to determine this just as cheaply, and requires no additional
initialisation.
This patch removes perf_event_context::type, and modifies existing users
Currently perf_event_context::type is used to determine whether a
context is cpu-bound or task-bound. However perf_event_context::task can
be used to determine this just as cheaply, and requires no additional
initialisation.
This patch removes perf_event_context::type, and modifies existing users
6 matches
Mail list logo