Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933554AbbGUSIU (ORCPT ); Tue, 21 Jul 2015 14:08:20 -0400 Received: from mail-ie0-f175.google.com ([209.85.223.175]:33227 "EHLO mail-ie0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933392AbbGUSIS (ORCPT ); Tue, 21 Jul 2015 14:08:18 -0400 From: Vince Weaver X-Google-Original-From: Vince Weaver Date: Tue, 21 Jul 2015 14:14:54 -0400 (EDT) To: linux-kernel@vger.kernel.org cc: Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo Subject: perf: multiplexing broken on amd fam16h? Message-ID: 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 Content-Length: 1699 Lines: 43 Hello I have a new AMD A8 system and perf multiplexing support is acting weird. If I run the perf_event_tests check_multiplexing test it fails like this: Event TotalCount RawCount Scale ScaledCount Error 0 500282143 150403975 -2.00 (c8050b5 fffffffff9c224ef) -300807950 160.13% So the problem is that the TOTAL_TIME_RUNNING value is negative, which as far as I know shouldn't be possible. I can't seem to track down why this would happen, and the same kernel (4.2-rc3) running on a Haswell machine doesn't have this problem. I tried to replicate the problem using perf, but for some reason I can't get perf to multiplex on any of my machines. That used to transparently work didn't it? here's the result on the haswell machine perf stat -e cycles,instructions,cycles,instructions,cycles,instructions,cycles,instructions sleep 5 Performance counter stats for 'sleep 5': 1,354,527 cycles 1,934,694 instructions # 1.76 insns per cycle 1,521,148 cycles 1,934,694 instructions # 1.76 insns per cycle 1,521,148 cycles 1,223,321 instructions # 1.11 insns per cycle [13.61%] cycles instructions 5.003651781 seconds time elapsed Vince -- 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/