Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758584Ab3HMQkW (ORCPT ); Tue, 13 Aug 2013 12:40:22 -0400 Received: from mx1.redhat.com ([209.132.183.28]:55871 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752176Ab3HMQkV (ORCPT ); Tue, 13 Aug 2013 12:40:21 -0400 From: Jiri Olsa To: linux-kernel@vger.kernel.org Cc: Jiri Olsa , Corey Ashford , Frederic Weisbecker , Paul Mackerras , Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , Andi Kleen , Stephane Eranian Subject: [RFC 0/2] perf: Fixing throttling related WARN Date: Tue, 13 Aug 2013 18:39:10 +0200 Message-Id: <1376411952-16718-1-git-send-email-jolsa@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1165 Lines: 32 hi, we managed to trigger perf WARN (described in patch 2), but only on AMD system with 48 CPUs. I believe the reason is a race in throttling code and I tried to fix it. So far my testing looks ok, but I suspect I broke something else.. ;-) thanks for comments, jirka Signed-off-by: Jiri Olsa Cc: Corey Ashford Cc: Frederic Weisbecker Cc: Paul Mackerras Cc: Peter Zijlstra Cc: Ingo Molnar Cc: Arnaldo Carvalho de Melo Cc: Andi Kleen Cc: Stephane Eranian --- arch/x86/kernel/cpu/perf_event_intel.c | 4 +++- include/linux/perf_event.h | 2 +- kernel/events/core.c | 67 +++++++++++++++++++++++++++++++++++++++---------------------------- 3 files changed, 43 insertions(+), 30 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/