From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752369AbbFKMOU (ORCPT ); Thu, 11 Jun 2015 08:14:20 -0400 Received: from mga11.intel.com ([192.55.52.93]:8299 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751818AbbFKMOG (ORCPT ); Thu, 11 Jun 2015 08:14:06 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,595,1427785200"; d="scan'208";a="506641086" From: Alexander Shishkin To: Peter Zijlstra , Ingo Molnar Cc: linux-kernel@vger.kernel.org, adrian.hunter@intel.com, x86@kernel.org, hpa@zytor.com, acme@infradead.org, Alexander Shishkin Subject: [PATCH 0/2] perf/x86/intel: Fixes for PT and BTS Date: Thu, 11 Jun 2015 15:13:55 +0300 Message-Id: <1434024837-9916-1-git-send-email-alexander.shishkin@linux.intel.com> X-Mailer: git-send-email 2.1.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Peter and Ingo, I have here two fixes for 4.1, both of which are basically results of not testing code properly with the NMI watchdog disabled, so one lesson learned here. One bug results in trace data loss and unknown NMI warnings and the other one is a NULL pointer dereference. The latter might need to be revisited in the future as we're now handling PT PMIs from intel_pmu_handle_irq() and we might want to change that. On the other hand, PT and x86_pmu share the PMI status register, so from that angle it kind of makes sense. But until such time as we decide to sort it out, the proposed fix should do nicely. Alexander Shishkin (2): perf/x86/intel/bts: Fix DS area sharing with x86_pmu events perf/x86/intel: Fix PMI handling for Intel PT arch/x86/kernel/cpu/perf_event.c | 70 +++++++++++++++++++++--------- arch/x86/kernel/cpu/perf_event.h | 4 ++ arch/x86/kernel/cpu/perf_event_intel_bts.c | 9 ++++ 3 files changed, 63 insertions(+), 20 deletions(-) -- 2.1.4