From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753089Ab1A0TMx (ORCPT ); Thu, 27 Jan 2011 14:12:53 -0500 Received: from mx1.redhat.com ([209.132.183.28]:45667 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751726Ab1A0TMw (ORCPT ); Thu, 27 Jan 2011 14:12:52 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Roland McGrath To: Peter Zijlstra X-Fcc: ~/Mail/linus Cc: Srikar Dronamraju , Ingo Molnar , Steven Rostedt , Arnaldo Carvalho de Melo , Linus Torvalds , Masami Hiramatsu , Christoph Hellwig , Andi Kleen , Oleg Nesterov , Andrew Morton , SystemTap , Jim Keniston , Frederic Weisbecker , Ananth N Mavinakayanahalli , LKML , "Paul E. McKenney" Subject: Re: [RFC] [PATCH 2.6.37-rc5-tip 13/20] 13: x86: x86 specific probe handling In-Reply-To: Peter Zijlstra's message of Thursday, 27 January 2011 11:22:13 +0100 <1296123733.15234.53.camel@laptop> References: <20101216095714.23751.52601.sendpatchset@localhost6.localdomain6> <20101216095947.23751.75003.sendpatchset@localhost6.localdomain6> <1295963783.28776.1061.camel@laptop> <20110127094041.GR19725@linux.vnet.ibm.com> <1296123733.15234.53.camel@laptop> X-Antipastobozoticataclysm: When George Bush projectile vomits antipasto on the Japanese. Message-Id: <20110127191146.DB22F180999@magilla.sf.frob.com> Date: Thu, 27 Jan 2011 11:11:46 -0800 (PST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > But I'll leave this to the x86 people who actually know the intricacies > of the single step cruft, I was just wondering why you weren't using (or > extending) the existing code. The hairy aspects of the step.c code are hairy (and not usable at interrupt level) because they do some instruction analysis. Since uprobes already does its own instruction analysis, reusing step.c's separate hacks makes less sense to me than integrating knowledge of the single-step vs pushf/popf issues into the uprobes instruction analysis. That said, there is further nontriviality just to do with the block-step support and with not clobbering user-visible usage of TF in eflags, which uprobes needs to handle as well. It makes sense to share that code rather than repeating it, even if that entails changes to the step.c code. Thanks, Roland