From: Ingo Molnar <mingo@kernel.org>
To: "Andy Lutomirski" <luto@kernel.org>,
"Frédéric Weisbecker" <fweisbec@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, Brian Gerst <brgerst@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
X86 ML <x86@kernel.org>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Subject: Re: [PATCH 0/3] perf: hw_breakpoint safety improvements
Date: Fri, 31 Jul 2015 10:10:31 +0200 [thread overview]
Message-ID: <20150731081031.GA13438@gmail.com> (raw)
In-Reply-To: <cover.1438312874.git.luto@kernel.org>
* Andy Lutomirski <luto@kernel.org> wrote:
> Hi, Peter-
>
> Here are some baby steps toward eliminating nested NMIs. What do
> you think?
>
> Andy Lutomirski (3):
> x86/perf/hw_breakpoint: Disallow kernel breakpoints unless kprobe-safe
> x86/perf/hw_breakpoint: Improve range breakpoint validation
> x86/perf/hw_breakpoint: Fix check for kernelspace breakpoints
>
> arch/x86/kernel/hw_breakpoint.c | 31 ++++++++++++++++++++++++++++++-
> include/linux/kprobes.h | 2 ++
> kernel/kprobes.c | 2 +-
> 3 files changed, 33 insertions(+), 2 deletions(-)
Looks good to me at first glance. Cc:-ed Frederic who wrote and maintains these
bits. Frederic, what do you think?
Thanks,
Ingo
next prev parent reply other threads:[~2015-07-31 8:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 3:32 Andy Lutomirski
2015-07-31 3:32 ` [PATCH 1/3] x86/perf/hw_breakpoint: Disallow kernel breakpoints unless kprobe-safe Andy Lutomirski
2015-08-04 8:54 ` [tip:perf/core] perf/x86/hw_breakpoints: " tip-bot for Andy Lutomirski
2015-08-04 15:51 ` [PATCH 1/3] x86/perf/hw_breakpoint: " Frederic Weisbecker
2015-08-04 23:29 ` 平松雅巳 / HIRAMATU，MASAMI
2015-09-01 10:57 ` Frederic Weisbecker
2015-09-01 11:36 ` Peter Zijlstra
2015-09-01 11:41 ` Peter Zijlstra
2015-07-31 3:32 ` [PATCH 2/3] x86/perf/hw_breakpoint: Improve range breakpoint validation Andy Lutomirski
2015-08-04 8:54 ` [tip:perf/core] perf/x86/hw_breakpoints: " tip-bot for Andy Lutomirski
2015-07-31 3:32 ` [PATCH 3/3] x86/perf/hw_breakpoint: Fix check for kernelspace breakpoints Andy Lutomirski
2015-08-04 8:54 ` [tip:perf/core] perf/x86/hw_breakpoints: Fix check for kernel-space breakpoints tip-bot for Andy Lutomirski
2015-08-04 16:13 ` [PATCH 3/3] x86/perf/hw_breakpoint: Fix check for kernelspace breakpoints Frederic Weisbecker
2015-07-31 8:10 ` Ingo Molnar [this message]
2015-07-31 8:21 ` [PATCH 0/3] perf: hw_breakpoint safety improvements Peter Zijlstra
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=20150731081031.GA13438@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
Powered by JetHome