From: Oleg Nesterov <oleg@redhat.com>
To: Denys Vlasenko <dvlasenk@redhat.com>
Cc: linux-kernel@vger.kernel.org, Jim Keniston <jkenisto@us.ibm.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Subject: Re: [PATCH v2] uprobes: simplify rip-relative handling
Date: Mon, 28 Apr 2014 17:31:43 +0200 [thread overview]
Message-ID: <20140428153143.GA20901@redhat.com> (raw)
In-Reply-To: <1398697605-7519-1-git-send-email-dvlasenk@redhat.com>
On 04/28, Denys Vlasenko wrote:
>
> It is possible to replace rip-relative addressing mode
> with addressing mode of the same length: (reg+disp32).
> This eliminates the need to fix up immediate
> and instruction length.
"and change instruction length", I presume.
I like this patch very much, and I would be happy to ack everything
except this part:
> @@ -307,22 +313,13 @@ static void riprel_analyze(struct arch_uprobe *auprobe, struct insn *insn)
> * #1) for the scratch register.
> */
> auprobe->def.fixups |= UPROBE_FIX_RIP_CX;
> - /* Change modrm from 00 000 101 to 00 000 001. */
> - *cursor = 0x1;
> + /* Change modrm from 00 000 101 to 10 000 001. */
> + *cursor = 0x81;
> } else {
> /* Use %rax (register #0) for the scratch register. */
> auprobe->def.fixups |= UPROBE_FIX_RIP_AX;
> - /* Change modrm from 00 xxx 101 to 00 xxx 000 */
> - *cursor = (reg << 3);
> - }
> -
> - /* Target address = address of next instruction + (signed) offset */
> - auprobe->def.riprel_target = (long)insn->length + insn->displacement.value;
> -
> - /* Displacement field is gone; slide immediate field (if any) over. */
> - if (insn->immediate.nbytes) {
> - cursor++;
> - memmove(cursor, cursor + insn->displacement.nbytes, insn->immediate.nbytes);
> + /* Change modrm from 00 xxx 101 to 10 xxx 000 */
> + *cursor = (reg << 3) | 0x80;
> }
As you know, this is black magic for me.
Masami, Jim, please review and ack/nack?
> @@ -343,26 +340,17 @@ static void riprel_pre_xol(struct arch_uprobe *auprobe, struct pt_regs *regs)
> unsigned long *sr = scratch_reg(auprobe, regs);
>
> utask->autask.saved_scratch_register = *sr;
> - *sr = utask->vaddr + auprobe->def.riprel_target;
> + *sr = utask->vaddr + (int)auprobe->def.ilen;
^^^^^
Why? This is pointless and even misleading. I'll remove this part if you
do not object.
Oleg.
prev parent reply other threads:[~2014-04-28 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 15:06 Denys Vlasenko
2014-04-28 15:31 ` Oleg Nesterov [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=20140428153143.GA20901@redhat.com \
--to=oleg@redhat.com \
--cc=dvlasenk@redhat.com \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.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
Powered by JetHome