From: Masami Hiramatsu <mhiramat@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
lkml <linux-kernel@vger.kernel.org>,
Jim Keniston <jkenisto@us.ibm.com>,
"H. Peter Anvin" <hpa@zytor.com>,
systemtap <systemtap@sources.redhat.com>,
DLE <dle-develop@lists.sourceforge.net>
Subject: Re: [PATCH -tip perf/probes 0/2] x86 insn decoder bugfixes
Date: Wed, 21 Oct 2009 11:57:35 -0400 [thread overview]
Message-ID: <4ADF2F6F.1040300@redhat.com> (raw)
In-Reply-To: <4ADF1E0B.5010708@redhat.com>
Masami Hiramatsu wrote:
> Ingo Molnar wrote:
>>
>> there's still build failures:
>>
>> TEST posttest
>> Error: ffffffff8103b917: c5 59 fc ff vpaddb %xmm7,%xmm4,%xmm15
>> Error: objdump says 4 bytes, but insn_get_length() says 3 (attr:8000)
>> make[1]: *** [posttest] Error 2
>> make: *** [bzImage] Error 2
>
> Aah, that's the AVX code...
> I assume, random-data-byte-sequence in the kernel binary
> contains it.
Hmm, I've found the actual code.
ffffffff81043917 <xen_sysret32_reloc>:
ffffffff81043917: c5 59 fc ff vpaddb %xmm7,%xmm4,%xmm15
---
ENTRY(xen_sysret32)
/*
* We're already on the usermode stack at this point, but
* still with the kernel gs, so we can easily switch back
*/
movq %rsp, PER_CPU_VAR(old_rsp)
movq PER_CPU_VAR(kernel_stack), %rsp
pushq $__USER32_DS
pushq PER_CPU_VAR(old_rsp)
pushq %r11
pushq $__USER32_CS
pushq %rcx
pushq $VGCF_in_syscall
1: jmp hypercall_iret
ENDPATCH(xen_sysret32)
RELOC(xen_sysret32, 1b+1)
---
#define RELOC(x, v) .globl x##_reloc; x##_reloc=v
---
OK, it's not a random, but a data in kernel text.
Anyway, I'll add AVX support then.
Thank you,
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America), Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
prev parent reply other threads:[~2009-10-21 15:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 16:55 [PATCH -tip perf/probes 0/2] x86 insn decoder bugfixes Masami Hiramatsu
2009-10-20 16:55 ` [PATCH -tip perf/probes 1/2] x86: Fix group attribute decoding bug Masami Hiramatsu
2009-10-24 1:03 ` [tip:branch?] " tip-bot for Masami Hiramatsu
2009-10-20 16:55 ` [PATCH -tip perf/probes 2/2] x86: Add AES opcodes to opcode map Masami Hiramatsu
2009-10-24 1:03 ` [tip:branch?] " tip-bot for Masami Hiramatsu
2009-10-24 1:03 ` [tip:branch?] x86, instruction decoder: Fix test_get_len build rules tip-bot for Ingo Molnar
2009-10-21 11:26 ` [PATCH -tip perf/probes 0/2] x86 insn decoder bugfixes Ingo Molnar
2009-10-21 12:21 ` Ingo Molnar
2009-10-21 14:43 ` Masami Hiramatsu
2009-10-21 15:57 ` Masami Hiramatsu [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=4ADF2F6F.1040300@redhat.com \
--to=mhiramat@redhat.com \
--cc=dle-develop@lists.sourceforge.net \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.