public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@redhat.com>
To: Ingo Molnar <mingo@elte.hu>, Jim Keniston <jkenisto@us.ibm.com>
Cc: Avi Kivity <avi@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>,
	kvm@vger.kernel.org, systemtap-ml <systemtap@sources.redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Vegard Nossum <vegard.nossum@gmail.com>
Subject: Re: [PATCH -tip 0/6 V4] tracing: kprobe-based event tracer
Date: Fri, 03 Apr 2009 12:55:12 -0400	[thread overview]
Message-ID: <49D63F70.7040308@redhat.com> (raw)
In-Reply-To: <20090403142325.GA14932@elte.hu>

Ingo Molnar wrote:
> * Masami Hiramatsu <mhiramat@redhat.com> wrote:
> 
>> Hmm, I'd like to know actually kvm aims to emulate all kinds of 
>> instructions. If so, I might find some bugs in x86_emulate.c. 
>> However, I don't know all bugs. To find all of them, we have to 
>> port x86_emulate.c to user-space, decode binaries with it, and 
>> compare its output with another decoder, as Jim had done with 
>> insn.c.
>>
>> https://www.redhat.com/archives/utrace-devel/2009-March/msg00031.html
> 
> btw., i'd suggest we put a build time check for this into the kernel 
> version as well. For example to decode the vmlinux via objdump, run 
> it through your decoder as well and compare the results. Put under a 
> CONFIG_DEBUG_X86_DECODER_TEST kind of (deault-off) build-time 
> self-test.
> 
> This would ensure that the kernel we are running is fully supported 
> by the decoder - even as GCC/GAS starts using new instructions, etc. 
> 
> How does this sound to you?

Thanks! That is a good idea.
Jim, would you think you can port your script into kernel tree?

Thank you,

-- 
Masami Hiramatsu

Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division

e-mail: mhiramat@redhat.com


  reply	other threads:[~2009-04-03 16:56 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
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 [this message]
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=49D63F70.7040308@redhat.com \
    --to=mhiramat@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=ananth@in.ibm.com \
    --cc=andi@firstfloor.org \
    --cc=avi@redhat.com \
    --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=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=systemtap@sources.redhat.com \
    --cc=vegard.nossum@gmail.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