be simpler than managing XOL vma. :-)
Thank you,
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America), Inc.
Software Solutions Division
e-mail: mhira...@redhat.com
as Andi said, using jump instead of int3 in userspace
has 2GB address space limitation. It's not a problem for kernel
inside, but a big problem in userspace.
Thank you,
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America), Inc.
Software Solutions Division
e-mail: mhira
) instructions.(even
it already supported AVX) But I think it's not so hard to add it.
Thank you,
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America), Inc.
Software Solutions Division
e-mail: mhira...@redhat.com
Jim Keniston wrote:
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
$$ /debug/tracing/set_ftrace_pid
echo function /debug/tracing/current_tracer
exec $*
I recommend you to add below line at the end of the script,
from my experience. :)
echo nop /debug/tracing/current_tracer
Thank you,
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America), Inc
Masami Hiramatsu wrote:
Steven Rostedt wrote:
On Tue, 2010-01-12 at 05:54 +0100, Frederic Weisbecker wrote:
Now what if I want to launch ls and want to profile a function
inside. What can I do with a trace event. I can't create the
probe event based on a pid as I don't know it in advance.
I
Hi Jim,
Jim Keniston wrote:
On Fri, 2009-02-27 at 16:20 -0500, Masami Hiramatsu wrote:
...
Here are a patch against your code and an example code for
instruction length decoder.
Curiously, KVM's instruction decoder does not completely
cover all instructions(especially, Jcc/test...).
I had
on it. After tested code, I'd like to post the insn_x86 code.
Thank you,
Thanks.
Jim
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division
e-mail: mhira...@redhat.com
TIF_SYSCALL_TRACE.)
I agree that.
I think if I can set TIF_SYSCALL_TRACE on each process safely, it can work
with utrace global tracing too.
In that case, I can move to utrace global tracing feature.
Thank you,
Thanks,
Roland
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America
