Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752715AbbLJW0p (ORCPT ); Thu, 10 Dec 2015 17:26:45 -0500 Received: from mail-io0-f196.google.com ([209.85.223.196]:33529 "EHLO mail-io0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751647AbbLJW0n (ORCPT ); Thu, 10 Dec 2015 17:26:43 -0500 MIME-Version: 1.0 In-Reply-To: References: Date: Thu, 10 Dec 2015 15:26:43 -0700 Message-ID: Subject: Re: [PATCH 1/1] Fix int1 recursion when no perf_bp_event is registeredy From: Jeff Merkey To: Thomas Gleixner Cc: Andy Lutomirski , LKML , Ingo Molnar , "H. Peter Anvin" , X86 ML , Peter Zijlstra , Andy Lutomirski , Masami Hiramatsu , Steven Rostedt , Borislav Petkov , Jiri Olsa Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1324 Lines: 35 I'll submit a second patch later this evening with a graceful message when this happens. I need to look over this code path -- its in a very mature section of code and detecting this condition (bp not being present) may break other code paths and subsystems ifs not done very carefully. The current dr7 check works and I have tested this code, but does not print a message. On 12/10/15, Thomas Gleixner wrote: > On Thu, 10 Dec 2015, Andy Lutomirski wrote: >> On brief inspection, this smells like a microcode bug. Can you send >> /proc/cpuinfo output? >> >> If this is the issue, I'm not sure we want to be in the business of >> working around localized microcode bugs and, if we do, then I think we >> should explicitly detect the bug and log about it. > > I think we should handle such stuff gracefully. Yes, we should log it > and we also should check what the contents of the debug registers are. > > If dr7 has a break point enabled w/o perf having one installed then we > know that someone did a horrible hackery .... > > Thanks, > > tglx > > > -- 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/