Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753489AbbLCUJT (ORCPT ); Thu, 3 Dec 2015 15:09:19 -0500 Received: from mail-pf0-f181.google.com ([209.85.192.181]:34392 "EHLO mail-pf0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753387AbbLCUJR (ORCPT ); Thu, 3 Dec 2015 15:09:17 -0500 X-Greylist: delayed 359 seconds by postgrey-1.27 at vger.kernel.org; Thu, 03 Dec 2015 15:09:17 EST From: Stephane Eranian To: linux-kernel@vger.kernel.org Cc: acme@redhat.com, peterz@infradead.org, mingo@elte.hu, ak@linux.intel.com, kan.liang@intel.com Subject: [PATCH v2 0/2] perf/x86: fixes and improvement for Intel Atom PEBS support Date: Thu, 3 Dec 2015 21:03:08 +0100 Message-Id: <1449172990-30183-1-git-send-email-eranian@google.com> X-Mailer: git-send-email 1.9.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1157 Lines: 30 This short series fixes total breakage of Intel Atom PEBS support in recent kernels. The problems were introduced with the changes in the PEBS logic to handle deeper buffer. The first patch fixes PEBS and LBR problems, including NULL pointers, wrong pointer arithmetic, and wrong pebs record layout assumption. The second patch adds an alias for cycles:pp to Intel Atom given that perf record/top uses cycles:pp nowadays. In V2, we removed the alias function specific to Atom use use the one from Core2 because it is identical as suggested by Kan Liang. Stephane Eranian (2): perf/x86: fix PEBS and LBR issues on Intel Atom perf/x86: enable cycles:pp for Intel Atom arch/x86/kernel/cpu/perf_event_intel.c | 1 + arch/x86/kernel/cpu/perf_event_intel_ds.c | 11 ++++++++++- arch/x86/kernel/cpu/perf_event_intel_lbr.c | 11 +++++++---- 3 files changed, 18 insertions(+), 5 deletions(-) -- 1.9.1 -- 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/