From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750839AbbJAVcl (ORCPT ); Thu, 1 Oct 2015 17:32:41 -0400 Received: from ou.quest-ce.net ([195.154.187.82]:40402 "EHLO ou.quest-ce.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750745AbbJAVck (ORCPT ); Thu, 1 Oct 2015 17:32:40 -0400 Message-ID: <1443735136.3188.22.camel@opteya.com> From: Yann Droneaud To: Jiri Olsa Cc: Adrian Hunter , David Ahern , Frederic Weisbecker , Jiri Olsa , Namhyung Kim , Paul Mackerras , Peter Zijlstra , Stephane Eranian , William Cohen , linux-kernel@vger.kernel.org Date: Thu, 01 Oct 2015 23:32:16 +0200 In-Reply-To: <20151001205247.GA4445@krava.redhat.com> References: <6b909f221c9b7c7a06fd2beed8a29586fbf86932.1443708092.git.ydroneaud@opteya.com> <20151001205247.GA4445@krava.redhat.com> Organization: OPTEYA Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.16.5 (3.16.5-3.fc22) Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-SA-Exim-Connect-IP: 2a01:e35:2e9f:6ac0:78e9:a807:dfc5:93d3 X-SA-Exim-Mail-From: ydroneaud@opteya.com Subject: Re: [PATCH v2 1/2] perf tools: shortcut PERF_FLAG_FD_CLOEXEC probing in case of EBUSY error X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on ou.quest-ce.net) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Le jeudi 01 octobre 2015 à 22:52 +0200, Jiri Olsa a écrit : > On Thu, Oct 01, 2015 at 05:16:25PM +0200, Yann Droneaud wrote: > > This patch is a simplification of the logic introduced as part of > > commit 63914aca8f7e ('perf tools: Show better error message in case > > we fail to open counters due to EBUSY error'): > > if EBUSY is reported by perf_event_open(), it will not be possible > > to probe PERF_FLAG_FD_CLOEXEC, so it's safe to leave early. > > > > It should be noted that -EBUSY errors are not really expected here > > since commit 038fa0b9739d ('perf tools: Fix PERF_FLAG_FD_CLOEXEC > > flag probing event type open counters due to EBUSY error'): > > the perf event type used now should be safe to use regarding -EBUSY > > error. > > > > Cc: Adrian Hunter > > Cc: David Ahern > > Cc: Frederic Weisbecker > > Cc: Jiri Olsa > > Cc: Namhyung Kim > > Cc: Paul Mackerras > > Cc: Peter Zijlstra > > Cc: Stephane Eranian > > Cc: William Cohen > > Link: > > http://lkml.kernel.org/r/cover.1443708092.git.ydroneaud@opteya.com > > Signed-off-by: Yann Droneaud > > --- > > tools/perf/util/cloexec.c | 8 ++++++-- > > 1 file changed, 6 insertions(+), 2 deletions(-) > > > > diff --git a/tools/perf/util/cloexec.c b/tools/perf/util/cloexec.c > > index 2babddaa2481..be226d293c91 100644 > > --- a/tools/perf/util/cloexec.c > > +++ b/tools/perf/util/cloexec.c > > @@ -56,7 +56,11 @@ static int perf_flag_probe(void) > > return 1; > > } > > > > - WARN_ONCE(err != EINVAL && err != EBUSY, > > + /* ignore busy errors */ > > + if (err == EBUSY) > > + return -1; > > so what's now the error message in case we get EBUSY ? > None, just as it does currently. perf_event_open_cloexec_flag() will still will return 0 just like PERF_FLAG_FD_CLOEXEC was not available. Handling -EBUSY is left to the function which will try to make use of perf_event_open(). Regards. -- Yann Droneaud OPTEYA