linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: David Carrillo-Cisneros <davidcc@google.com>
Cc: linux-kernel@vger.kernel.org, "x86@kernel.org" <x86@kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andi Kleen <ak@linux.intel.com>, Kan Liang <kan.liang@intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Vegard Nossum <vegard.nossum@gmail.com>,
	Paul Turner <pjt@google.com>,
	Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH v2 1/4] perf/core: check return value of perf_event_read IPI
Date: Wed, 10 Aug 2016 13:04:38 +0200	[thread overview]
Message-ID: <20160810110437.GB14283@gmail.com> (raw)
In-Reply-To: <1470539577-102094-2-git-send-email-davidcc@google.com>


* David Carrillo-Cisneros <davidcc@google.com> wrote:

> The call to smp_call_function_single in perf_event_read() may fail and,
> when it does, its error value is the one to return.
> 
> Signed-off-by: David Carrillo-Cisneros <davidcc@google.com>
> Reviewed-by: Stephane Eranian <eranian@google.com>
> ---
>  kernel/events/core.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index 9345028..96523fd 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -3469,9 +3469,9 @@ static int perf_event_read(struct perf_event *event, bool group)
>  			.group = group,
>  			.ret = 0,
>  		};
> -		smp_call_function_single(event->oncpu,
> -					 __perf_event_read, &data, 1);
> -		ret = data.ret;
> +		ret = smp_call_function_single(event->oncpu,
> +					       __perf_event_read, &data, 1);
> +		ret = ret ? : data.ret;
>  	} else if (event->state == PERF_EVENT_STATE_INACTIVE) {
>  		struct perf_event_context *ctx = event->ctx;
>  		unsigned long flags;

Please also describe the symptoms of the bug - under what circumstances may the 
smp-call fail and how does the user notice?

Thanks,

        Ingo

  reply	other threads:[~2016-08-10 20:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-07  3:12 [PATCH v2 0/4] remove unnecessary IPI reading uncore events David Carrillo-Cisneros
2016-08-07  3:12 ` [PATCH v2 1/4] perf/core: check return value of perf_event_read IPI David Carrillo-Cisneros
2016-08-10 11:04   ` Ingo Molnar [this message]
2016-08-17 20:53     ` David Carrillo-Cisneros
2016-08-07  3:12 ` [PATCH v2 2/4] perf/core: generalize event->group_flags David Carrillo-Cisneros
2016-08-07  3:12 ` [PATCH v2 3/4] perf/core: introduce PMU_EV_CAP_READ_ACTIVE_PKG David Carrillo-Cisneros
2016-08-07 19:10   ` Nilay Vaish
2016-08-07 20:10     ` David Carrillo-Cisneros
2016-08-08 16:12       ` Nilay Vaish
2016-08-09  5:04         ` David Carrillo-Cisneros
2016-08-09 22:28         ` [PATCH " David Carrillo-Cisneros
2016-08-10 18:27           ` Nilay Vaish
2016-08-08 10:00   ` [PATCH v3 " David Carrillo-Cisneros
2016-08-07  3:12 ` [PATCH v2 4/4] perf/x86: use PMUEF_READ_CPU_PKG in uncore events David Carrillo-Cisneros
2016-08-10 18:30 ` [PATCH v2 0/4] remove unnecessary IPI reading " Nilay Vaish

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160810110437.GB14283@gmail.com \
    --to=mingo@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=davidcc@google.com \
    --cc=eranian@google.com \
    --cc=kan.liang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=pjt@google.com \
    --cc=tglx@linutronix.de \
    --cc=vegard.nossum@gmail.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).