From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arjan van de Ven Subject: Re: linux-next: add utrace tree Date: Mon, 8 Feb 2010 01:53:49 -0800 Message-ID: <20100208015349.36a12efe@infradead.org> References: <1264575134.4283.1983.camel@laptop> <1264600792.31321.464.camel@gandalf.stny.rr.com> <4B607B1A.3080007@zytor.com> <20100208065425.GB1290@ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20100208065425.GB1290@ucw.cz> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: utrace-devel-bounces@redhat.com Errors-To: utrace-devel-bounces@redhat.com To: Pavel Machek Cc: Stephen Rothwell , Kyle Moffett , Arnaldo Carvalho de Melo , Peter Zijlstra , Fr??d??ric Weisbecker , "H. Peter Anvin" , Oleg Nesterov , rostedt@goodmis.org, LKML , Tromey , "Frank Ch. Eigler" , linux-next@vger.kernel.org, Tom@redhat.com, utrace-devel@redhat.com, Linus Torvalds , Thomas Gleixner List-Id: linux-next.vger.kernel.org On Mon, 8 Feb 2010 07:54:25 +0100 Pavel Machek wrote: > > No, it has nothing to do with ring. It has to do with modifying > > code that another CPU could be executing at the same time, and with > > modifying code on the same processor through another virtual alias > > (they are different issues.) The same issues apply regardless of > > the CPL of the processor. > > ...but these are always 'there could be cpu bugs around' issues, > right? Like amd k6. AFAICT x86 always supported self-modifying code > without any extra barriers needed... self modifying code yes, cross modifying code no. -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org