[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200902132549.496605622@infradead.org>
Date: Wed, 02 Sep 2020 15:25:49 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: x86@...nel.org
Cc: linux-kernel@...r.kernel.org, Kyle Huey <me@...ehuey.com>,
Alexandre Chartre <alexandre.chartre@...cle.com>,
Robert O'Callahan <rocallahan@...il.com>,
"Paul E. McKenney" <paulmck@...nel.org>,
Frederic Weisbecker <frederic@...nel.org>,
Paolo Bonzini <pbonzini@...hat.com>,
Sean Christopherson <sean.j.christopherson@...el.com>,
Masami Hiramatsu <mhiramat@...nel.org>,
Petr Mladek <pmladek@...e.com>,
Steven Rostedt <rostedt@...dmis.org>,
Joel Fernandes <joel@...lfernandes.org>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
Juergen Gross <jgross@...e.com>,
Brian Gerst <brgerst@...il.com>,
Andy Lutomirski <luto@...nel.org>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Daniel Thompson <daniel.thompson@...aro.org>,
Peter Zijlstra <peterz@...radead.org>
Subject: [PATCH 00/13] x86/debug: Untangle handle_debug()
Hi,
The first two patches probably ought to go in x86/urgent, the rest (!RFC) can
go into x86/core and wait a bit.
handle_debug() is a mess, and now that we have separate user and kernel paths,
try and clean it up a bit.
There's two RFC patches at the end that impact the ptrace_{get,set}_debugreg(6)
ABI, I've no idea what, if anything, is expected of that or if anybody actually
cares about that. If I read the code correctly nothing actually consumes the
value from ptrace_set_debugreg(6).
Kyle, you seem to be pushing all this to the edge with RR, any clues?
Since v2:
- fixed (user) INT1 / icebp detection
- some further cleanups
- two additional RFC patches
Powered by blists - more mailing lists