From: Ingo Molnar <mingo@elte.hu>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Li Zefan <lizf@cn.fujitsu.com>
Subject: Re: [GIT PULL] tracing/kprobes: kprobes fixes
Date: Sat, 3 Oct 2009 12:49:23 +0200 [thread overview]
Message-ID: <20091003104923.GA3250@elte.hu> (raw)
In-Reply-To: <20091003103538.GA12263@elte.hu>
ok, -tip testing found this new failure:
TEST posttest
Error: ffffffff8106ac00: 66 0f 73 fd 04 pslldq $0x4,%xmm5
Error: objdump says 5 bytes, but insn_get_length() says 4 (attr:8000)
make[1]: *** [posttest] Error 2
make: *** [bzImage] Error 2
Ingo
prev parent reply other threads:[~2009-10-03 10:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 2:31 [GIT PULL] tracing/kprobes: kprobes fixes Frederic Weisbecker
2009-10-03 2:31 ` [PATCH 1/3] tracing/kprobes: Use global event perf buffers in kprobe tracer Frederic Weisbecker
2009-10-03 2:31 ` [PATCH 2/3] x86: Add VIA processor instructions in opcodes decoder Frederic Weisbecker
2009-10-03 2:31 ` [PATCH 3/3] tracing/ftrace: Fix to check create_event_dir() when adding new events Frederic Weisbecker
2009-10-03 10:35 ` [GIT PULL] tracing/kprobes: kprobes fixes Ingo Molnar
2009-10-03 10:49 ` Ingo Molnar [this message]
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=20091003104923.GA3250@elte.hu \
--to=mingo@elte.hu \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=rostedt@goodmis.org \
/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