From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752000AbdKVSKd (ORCPT ); Wed, 22 Nov 2017 13:10:33 -0500 Received: from one.firstfloor.org ([193.170.194.197]:52486 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751640AbdKVSKb (ORCPT ); Wed, 22 Nov 2017 13:10:31 -0500 Date: Wed, 22 Nov 2017 10:10:29 -0800 From: Andi Kleen To: Mathieu Desnoyers Cc: Andy Lutomirski , Andi Kleen , Peter Zijlstra , "Paul E. McKenney" , Boqun Feng , Dave Watson , linux-kernel , linux-api , Paul Turner , Andrew Morton , Russell King , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Andrew Hunter , Chris Lameter , Ben Maurer , rostedt , Josh Triplett , Linus Torvalds , Catalin Marinas , Will Deacon , Michael Kerrisk Subject: Re: [RFC PATCH for 4.15 v12 00/22] Restartable sequences and CPU op vector Message-ID: <20171122181028.GM2482@two.firstfloor.org> References: <20171121141900.18471-1-mathieu.desnoyers@efficios.com> <20171121172144.GL2482@two.firstfloor.org> <740195164.19702.1511301908907.JavaMail.zimbra@efficios.com> <718035530.20074.1511369023901.JavaMail.zimbra@efficios.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <718035530.20074.1511369023901.JavaMail.zimbra@efficios.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > If anyone ever reports that as a problem, I'll gladly fix it in the > > kernel. That's doable without an ABI change. If rseq-like things > > started breaking single-stepping, we can't just fix it in the kernel. AFAIK nobody ever complained about it since we have vsyscalls and vDSOs. > > Very true. And rseq does break both line-level and instruction-level > single-stepping. They can just set a break point after it and continue. In fact it could be even expressed to the debugger to do that automatically based on some dwarf extension. I also disagree that opv somehow "solves" debugging: it's a completely different code path that has nothing to do with the original code path. That's not debugging, that's at best a workaround. I don't think it's any better than the break point method. -Andi