From: Avi Kivity <avi@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Masami Hiramatsu <mhiramat@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <andi@firstfloor.org>,
Jim Keniston <jkenisto@us.ibm.com>,
kvm@vger.kernel.org, systemtap-ml <systemtap@sources.redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip 0/6 V4] tracing: kprobe-based event tracer
Date: Fri, 03 Apr 2009 15:17:06 +0300 [thread overview]
Message-ID: <49D5FE42.5080100@redhat.com> (raw)
In-Reply-To: <20090403121202.GI31399@elte.hu>
Ingo Molnar wrote:
>> kvm has three requirements not needed by kprobes:
>> - it wants to execute instructions, not just decode them, including
>> generating faults where appropriate
>> - it is performance critical
>> - it needs to support 16-bit, 32-bit, and 64-bit instructions simultaneously
>>
>> If an arch/x86/ decoder/emulator gives me these I'll gladly switch
>> to it. x86_emulate.c is high on my list of most disliked code.
>>
>
> Well, this has to be driven from the KVM side as the kprobes use
> will only be for decoding so if it's modified from the kprobes side
> the KVM-only functionality might regress.
>
> So ... we can do the library decoder for kprobes purposes, and
> someone versed in the KVM emulator can then combine the two.
>
Problem is, anyone versed in the kvm emulator will want to run as far
away from this work as possible.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-04-03 12:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 17:24 [PATCH -tip 0/6 V4] tracing: kprobe-based event tracer Masami Hiramatsu
2009-04-03 11:26 ` Ingo Molnar
2009-04-03 11:32 ` Andi Kleen
2009-04-03 11:50 ` Avi Kivity
2009-04-03 12:12 ` Ingo Molnar
2009-04-03 12:17 ` Avi Kivity [this message]
2009-04-03 12:26 ` Ingo Molnar
2009-04-03 12:33 ` Avi Kivity
2009-04-03 13:16 ` Vegard Nossum
2009-04-03 13:40 ` Avi Kivity
2009-04-03 13:52 ` Masami Hiramatsu
2009-04-05 19:37 ` Pekka Paalanen
2009-04-06 7:53 ` Avi Kivity
2009-04-03 12:25 ` Andi Kleen
2009-04-03 14:21 ` Masami Hiramatsu
2009-04-03 14:23 ` Ingo Molnar
2009-04-03 16:55 ` Masami Hiramatsu
2009-04-03 17:59 ` Jim Keniston
2009-04-03 14:30 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49D5FE42.5080100@redhat.com \
--to=avi@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=andi@firstfloor.org \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=jkenisto@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=systemtap@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox