Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753079AbZIYIZm (ORCPT ); Fri, 25 Sep 2009 04:25:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752974AbZIYIZi (ORCPT ); Fri, 25 Sep 2009 04:25:38 -0400 Received: from casper.infradead.org ([85.118.1.10]:38357 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752929AbZIYIZh (ORCPT ); Fri, 25 Sep 2009 04:25:37 -0400 Date: Fri, 25 Sep 2009 10:25:16 +0200 From: Arjan van de Ven To: Mathieu Desnoyers Cc: Ingo Molnar , "H. Peter Anvin" , Jason Baron , Thomas Gleixner , Steven Rostedt , Andi Kleen , linux-kernel@vger.kernel.org, Masami Hiramatsu , Prasanna S Panchamukhi , Rusty Lynch , Jim Keniston , Vamsi Krishna S , Suparna Bhattacharya , Nathan Sidwell , Dominique Toupin , Anton Massoud , Richard J Moore Subject: Re: Immediate values Message-ID: <20090925102516.2ef02414@infradead.org> In-Reply-To: <20090925073512.GA10346@Krystal> References: <20090924191642.GA19225@elte.hu> <20090924193422.GB2533@elte.hu> <20090925085119.2b77ea04@infradead.org> <20090925073512.GA10346@Krystal> Organization: Intel X-Mailer: Claws Mail 3.7.2 (GTK+ 2.14.7; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by casper.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1630 Lines: 45 On Fri, 25 Sep 2009 03:35:13 -0400 Mathieu Desnoyers wrote: > * Arjan van de Ven (arjan@infradead.org) wrote: > > On Thu, 24 Sep 2009 21:34:22 +0200 > > Ingo Molnar wrote: > > > [context for people CCed: see > http://lkml.org/lkml/2009/9/24/262] > > > > > > > > stopmachine is fine. > > > > more aggressive tricks are rather dicey. > > > > (cross modifying code that's being executed in ring 0 is ... not > > something CPU designers had in mind) > > > > Then, following your advice, kprobes should be re-designed to do a > stop_machine around the int3 breakpoint insertion ? And gdb > should be stopping all threads of a target process before inserting a > breakpoint. Therefore, I do not seem to be the only one confused about > Intel statement on this issue. you are oversimplifying what you are trying to do, and overstating what a ring 3 app and others do. But I'm not the one whom you'd need to convince, I don't design the CPU. The people who do are extremely frowning on cross modifying code, and Peter and I need to sit down with people who did many generations of CPU to figure out if your scheme is actually safe. And on the AMD side someone will need to do the same. -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/