[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.1.10.0808082050140.3707@gandalf.stny.rr.com>
Date: Fri, 8 Aug 2008 20:51:23 -0400 (EDT)
From: Steven Rostedt <rostedt@...dmis.org>
To: Jeremy Fitzhardinge <jeremy@...p.org>
cc: Andi Kleen <andi@...stfloor.org>,
Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
David Miller <davem@...emloft.net>,
Roland McGrath <roland@...hat.com>,
Ulrich Drepper <drepper@...hat.com>,
Rusty Russell <rusty@...tcorp.com.au>,
Gregory Haskins <ghaskins@...ell.com>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
"Luis Claudio R. Goncalves" <lclaudio@...g.org>,
Clark Williams <williams@...hat.com>
Subject: Re: [PATCH 0/5] ftrace: to kill a daemon
On Fri, 8 Aug 2008, Jeremy Fitzhardinge wrote:
> Steven Rostedt wrote:
> > I wish we had a true 5 byte nop.
>
> 0x66 0x66 0x66 0x66 0x90
>
But I quote you:
> Unfortunately, aside from P6_NOP5, none of the standard asm/nops.h nops
> are suitable. Something like "0x66, 0x66, 0x66, 0x66, 0x90" would work
> everywhere, but its possible putting more than 3 prefixes on the
> instruction will kick the decoder into a slow path, which may have a
> noticable effect.
I guess the next step is to test if it is slow.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists