From: Yonghong Song <yhs@fb.com>
To: David Laight <David.Laight@ACULAB.COM>,
"mingo@kernel.org" <mingo@kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"oleg@redhat.com" <oleg@redhat.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"ast@fb.com" <ast@fb.com>
Cc: "kernel-team@fb.com" <kernel-team@fb.com>
Subject: Re: [PATCH x86 v2] uprobe: emulate push insns for uprobe on x86
Date: Thu, 9 Nov 2017 09:22:10 -0800 [thread overview]
Message-ID: <4d290497-4b4a-2eb5-1b92-496b990c80b2@fb.com> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6DD00B73C7@AcuExch.aculab.com>
On 11/9/17 3:26 AM, David Laight wrote:
> From: Yonghong Song
>> Sent: 09 November 2017 00:55
>>
>> Uprobe is a tracing mechanism for userspace programs.
>> Typical uprobe will incur overhead of two traps.
>> First trap is caused by replaced trap insn, and
>> the second trap is to execute the original displaced
>> insn in user space.
>>
>> To reduce the overhead, kernel provides hooks
>> for architectures to emulate the original insn
>> and skip the second trap. In x86, emulation
>> is done for certain branch insns.
>>
>> This patch extends the emulation to "push <reg>"
>> insns. These insns are typical in the beginning
>> of the function. For example, bcc
> ...
>> diff --git a/arch/x86/include/asm/uprobes.h b/arch/x86/include/asm/uprobes.h
>> index 74f4c2f..f9d2b43 100644
>> --- a/arch/x86/include/asm/uprobes.h
>> +++ b/arch/x86/include/asm/uprobes.h
>> @@ -33,6 +33,11 @@ typedef u8 uprobe_opcode_t;
> ...
>> @@ -53,6 +59,10 @@ struct arch_uprobe {
>> u8 fixups;
>> u8 ilen;
>> } defparam;
>> + struct {
>> + u8 rex_prefix;
>
> Just call this 'reg_high' and set to 0 or 1.
Will do.
>
>> + u8 opc1;
>> + } push;
>> };
>> };
>>
>> diff --git a/arch/x86/kernel/uprobes.c b/arch/x86/kernel/uprobes.c
>> index a3755d2..5ace65c 100644
>> --- a/arch/x86/kernel/uprobes.c
>> +++ b/arch/x86/kernel/uprobes.c
>> @@ -640,11 +640,71 @@ static bool check_jmp_cond(struct arch_uprobe *auprobe, struct pt_regs *regs)
>> #undef COND
>> #undef CASE_COND
>>
>> -static bool branch_emulate_op(struct arch_uprobe *auprobe, struct pt_regs *regs)
>> +static unsigned long *get_push_reg_ptr(struct arch_uprobe *auprobe,
>> + struct pt_regs *regs)
>> {
>> - unsigned long new_ip = regs->ip += auprobe->branch.ilen;
>> - unsigned long offs = (long)auprobe->branch.offs;
>> +#if defined(CONFIG_X86_64)
>> + switch (auprobe->push.opc1) {
>> + case 0x50:
>> + return auprobe->push.rex_prefix ? ®s->r8 : ®s->ax;
>> + case 0x51:
>> + return auprobe->push.rex_prefix ? ®s->r9 : ®s->cx;
>> + case 0x52:
>> + return auprobe->push.rex_prefix ? ®s->r10 : ®s->dx;
>> + case 0x53:
>> + return auprobe->push.rex_prefix ? ®s->r11 : ®s->bx;
>> + case 0x54:
>> + return auprobe->push.rex_prefix ? ®s->r12 : ®s->sp;
>> + case 0x55:
>> + return auprobe->push.rex_prefix ? ®s->r13 : ®s->bp;
>> + case 0x56:
>> + return auprobe->push.rex_prefix ? ®s->r14 : ®s->si;
>> + }
>> +
>> + /* opc1 0x57 */
>> + return auprobe->push.rex_prefix ? ®s->r15 : ®s->di;
>
> The bottom of that switch statement is horrid....
> Actually why can't you sort out this address in the code that
> sets up 'reg_prefix' (etc);
Good suggestion. Will do.
>
> David
>
prev parent reply other threads:[~2017-11-09 17:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 0:54 Yonghong Song
2017-11-09 11:26 ` David Laight
2017-11-09 17:22 ` Yonghong Song [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=4d290497-4b4a-2eb5-1b92-496b990c80b2@fb.com \
--to=yhs@fb.com \
--cc=David.Laight@ACULAB.COM \
--cc=ast@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®