From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933283AbcH2NOy (ORCPT ); Mon, 29 Aug 2016 09:14:54 -0400 Received: from mail-it0-f68.google.com ([209.85.214.68]:35496 "EHLO mail-it0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933015AbcH2NOw (ORCPT ); Mon, 29 Aug 2016 09:14:52 -0400 From: Vince Weaver X-Google-Original-From: Vince Weaver Date: Mon, 29 Aug 2016 09:14:46 -0400 (EDT) X-X-Sender: vince@macbook-air To: Peter Zijlstra cc: Jiri Olsa , Vegard Nossum , Thomas Gleixner , Stephane Eranian , Vince Weaver , Ingo Molnar , David Carrillo-Cisneros , "H. Peter Anvin" , Kan Liang , Arnaldo Carvalho de Melo , Paul Turner , Linus Torvalds , LKML , Alexander Shishkin , linux-tip-commits@vger.kernel.org Subject: Re: [tip:perf/core] perf/core: Check return value of the perf_event_read() IPI In-Reply-To: <20160829130213.GF10168@twins.programming.kicks-ass.net> Message-ID: References: <1471467307-61171-2-git-send-email-davidcc@google.com> <20160822071737.GF4349@krava> <20160822082932.GA13171@krava> <20160822103823.GA2271@krava> <20160829100309.GS10121@twins.programming.kicks-ass.net> <20160829130213.GF10168@twins.programming.kicks-ass.net> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 29 Aug 2016, Peter Zijlstra wrote: > > The best I can come up with is something like: > > > do { > state = READ_ONCE(event->state); > if (state != ACTIVE) > break; > smp_rmb(); > cpu = READ_ONCE(event->cpu); > smp_rmb(); > } while (READ_ONCE(event->state) != state); > > > And I suppose perf_event_restart() should do the same thing... Let me > ponder this a wee bit more. the perf_fuzzer trips over this warning fairly regularly too, so once you have a patch you're happy with I can give it a test. I ordered a whole crate of null modem cables so I've got a whole bunch of serial consoles ready and raring to go. Maybe I can find out how the fuzzer crashes the new skylake machine, it doesn't leave anything useful in the syslog. Vince