mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Jeff Merkey <linux.mdb@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	X86 ML <x86@kernel.org>, Peter Zijlstra <peterz@infradead.org>,
	Andy Lutomirski <luto@kernel.org>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Borislav Petkov <bp@alien8.de>, Jiri Olsa <jolsa@kernel.org>
Subject: Re: [PATCH 1/1] Fix int1 recursion when no perf_bp_event is registeredy
Date: Thu, 10 Dec 2015 21:49:33 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.11.1512102050290.3623@nanos> (raw)
In-Reply-To: <CALCETrUaWxqyuyE2FqCs0ULPBdKMwCPtaoneyt4yBA8r5a5=yQ@mail.gmail.com>

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



  parent reply	other threads:[~2015-12-10 20:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-10  7:12 [PATCH 1/1] Fix int1 recursion when no perf_bp_event is registered Jeff Merkey
2015-12-10 18:55 ` Thomas Gleixner
2015-12-10 19:09   ` Andy Lutomirski
2015-12-10 19:20     ` Jiri Olsa
2015-12-10 19:25       ` Borislav Petkov
2015-12-10 20:49     ` Thomas Gleixner [this message]
2015-12-10 21:09       ` [PATCH 1/1] Fix int1 recursion when no perf_bp_event is registeredy Andy Lutomirski
2015-12-10 21:15         ` Thomas Gleixner
2015-12-10 21:26           ` Jeff Merkey
2015-12-10 21:16         ` Jeff Merkey
2015-12-14  8:09           ` Ingo Molnar
2015-12-14  8:13             ` Jeff Merkey
2015-12-14  8:26               ` Jeff Merkey
2015-12-14  9:28               ` Ingo Molnar
2015-12-14 17:52                 ` Jeff Merkey
2015-12-14 17:56                   ` Andy Lutomirski
2015-12-14 18:16                     ` Jeff Merkey
2015-12-14 18:18                     ` Jeff Merkey
2015-12-10 21:11       ` Jeff Merkey
2015-12-10 22:26       ` Jeff Merkey
2015-12-11  8:05       ` [PATCH v2 " Jeff Merkey
2015-12-11 19:04         ` Jeff Merkey
2015-12-13 23:11         ` Jeff Merkey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.11.1512102050290.3623@nanos \
    --to=tglx@linutronix.de \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux.mdb@gmail.com \
    --cc=luto@amacapital.net \
    --cc=luto@kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®