[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1263842482.5059.9.camel@localhost.localdomain>
Date: Mon, 18 Jan 2010 11:21:22 -0800
From: Jim Keniston <jkenisto@...ibm.com>
To: Masami Hiramatsu <mhiramat@...hat.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
Ingo Molnar <mingo@...e.hu>,
Arnaldo Carvalho de Melo <acme@...radead.org>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
utrace-devel <utrace-devel@...hat.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Maneesh Soni <maneesh@...ibm.com>,
Mark Wielaard <mjw@...hat.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] [PATCH 1/7] User Space Breakpoint Assistance Layer (UBP)
On Mon, 2010-01-18 at 10:58 -0500, Masami Hiramatsu wrote:
> Jim Keniston wrote:
> > Not really. For #3 (boosting), you need to know everything for #2,
> > plus be able to compute the length of each instruction -- which we can
> > now do for x86. To emulate an instruction (#4), you need to replicate
> > what it does, side-effects and all. The x86 instruction set seems to
> > be adding new floating-point instructions all the time, and I bet even
> > Masami doesn't know what they all do, but so far, they all seem to
> > adhere to the instruction-length rules encoded in Masami's instruction
> > decoder.
>
> Actually, current x86 decoder doesn't support FP(x87) instructions.(even
> it already supported AVX) But I think it's not so hard to add it.
>
At one point I verified that it worked for all the x87 instructions in
libm:
https://www.redhat.com/archives/utrace-devel/2009-March/msg00031.html
I'm pretty sure I tested mmx instructions as well. But I guess this was
before you rearranged the opcode tables.
Yeah, it wouldn't be hard to add back in, at least for purposes of
computing instruction lengths.
Jim
--
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