[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMmz+YnSSn3t=qSjfMX5H5Mp6QuTePkuLMjV7FO7at8z4TXu1Q@mail.gmail.com>
Date: Sun, 26 Nov 2017 22:50:27 -0800
From: Milind Chabbi <chabbi.milind@...il.com>
To: Milind Chabbi <chabbi.milind@...il.com>
Cc: Jiri Olsa <jolsa@...hat.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Paul Mackerras <paulus@...ba.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] perf/core: Enable the bp only if the .disable field is 0.
On Sun, Nov 26, 2017 at 10:43 PM, Milind Chabbi <chabbi.milind@...il.com> wrote:
> Signed-off-by: Milind Chabbi <chabbi.milind@...il.com>
> ---
> kernel/events/core.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index 35747a58ffb4..1b8eae85e9de 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -2659,7 +2659,8 @@ static int perf_event_modify_breakpoint(struct perf_event *bp,
> return err;
> }
>
> - _perf_event_enable(bp);
> + if (!attr->disabled)
> + _perf_event_enable(bp);
> return 0;
> }
>
> --
> 2.14.1
>
Hi Jirka,
Thanks for your changes for proper accounting of the bp.
This additional change is needed so that we do not enable the bp if
the user has not asked to enable it.
I did the testing for ioctl and it continues to show the significant
speedups that I had originally seen.
-Milind
Powered by blists - more mailing lists