From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751777AbdKVQmp (ORCPT ); Wed, 22 Nov 2017 11:42:45 -0500 Received: from mail.efficios.com ([167.114.142.141]:44336 "EHLO mail.efficios.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751303AbdKVQmn (ORCPT ); Wed, 22 Nov 2017 11:42:43 -0500 Date: Wed, 22 Nov 2017 16:43:43 +0000 (UTC) From: Mathieu Desnoyers To: Andy Lutomirski Cc: 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 Message-ID: <718035530.20074.1511369023901.JavaMail.zimbra@efficios.com> In-Reply-To: References: <20171121141900.18471-1-mathieu.desnoyers@efficios.com> <20171121172144.GL2482@two.firstfloor.org> <740195164.19702.1511301908907.JavaMail.zimbra@efficios.com> Subject: Re: [RFC PATCH for 4.15 v12 00/22] Restartable sequences and CPU op vector MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [167.114.142.141] X-Mailer: Zimbra 8.7.11_GA_1854 (ZimbraWebClient - FF52 (Linux)/8.7.11_GA_1854) Thread-Topic: Restartable sequences and CPU op vector Thread-Index: jOy0TMJBeK2J3huB3qQDAOap11fG4g== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org ----- On Nov 22, 2017, at 10:28 AM, Andy Lutomirski luto@amacapital.net wrote: > On Tue, Nov 21, 2017 at 2:05 PM, Mathieu Desnoyers > wrote: >> ----- On Nov 21, 2017, at 12:21 PM, Andi Kleen andi@firstfloor.org wrote: >> >>> On Tue, Nov 21, 2017 at 09:18:38AM -0500, Mathieu Desnoyers wrote: >>>> Hi, >>>> >>>> Following changes based on a thorough coding style and patch changelog >>>> review from Thomas Gleixner and Peter Zijlstra, I'm respinning this >>>> series for another RFC. >>>> >>> My suggestion would be that you also split out the opv system call. >>> That seems to be main contention point currently, and the restartable >>> sequences should be useful without it. >> >> I consider rseq to be incomplete and a pain to use in various scenarios >> without cpu_opv. >> >> About the contention point you refer to: >> >> Using vDSO as an example of how things should be done is just wrong: the >> vDSO interaction with debugger instruction single-stepping is broken, >> as I detailed in my previous email. >> > > 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. Very true. And rseq does break both line-level and instruction-level single-stepping. > > Also, there is one and only one vclock_gettime. Debuggers can easily > special-case it. For all I know, they already do. As my tests demonstrate, they don't. clock_gettime() vDSO currently breaks instruction-level single-stepping (istep) with gdb. I'll forward you the writeup I did on that a few days ago. Thanks, Mathieu -- Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com