mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "liaochang (A)" <liaochang1@huawei.com>
To: Jisheng Zhang <jszhang@kernel.org>
Cc: <paul.walmsley@sifive.com>, <palmer@dabbelt.com>,
	<aou@eecs.berkeley.edu>, <mhiramat@kernel.org>,
	<rostedt@goodmis.org>, <linux-riscv@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] riscv/kprobe: Optimize the performance of patching instruction slot
Date: Thu, 8 Sep 2022 09:43:45 +0800	[thread overview]
Message-ID: <a00328a1-47ee-3700-8cd8-1a9f4e0d7a2b@huawei.com> (raw)
In-Reply-To: <YxjTF2FlIJbbKq0p@xhacker>

Thanks for comment.

在 2022/9/8 1:21, Jisheng Zhang 写道:
> On Wed, Sep 07, 2022 at 10:33:27AM +0800, Liao Chang wrote:
>> Since no race condition occurs on each instruction slot, hence it is
>> safe to patch instruction slot without stopping machine.
> 
> hmm, IMHO there's race when arming kprobe under SMP, so stopping
> machine is necessary here. Maybe I misundertand something.
> 

It is indeed necessary to stop machine when arm kprobe under SMP,
but i don't think it need to stop machine when prepare instruction slot,
two reasons:

1. Instruction slot is dynamically allocated data.
2. Kernel would not execute instruction slot until original instruction
   is replaced by breakpoint.

>>
>> Signed-off-by: Liao Chang <liaochang1@huawei.com>
>> ---
>>  arch/riscv/kernel/probes/kprobes.c | 8 +++++---
>>  1 file changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/arch/riscv/kernel/probes/kprobes.c b/arch/riscv/kernel/probes/kprobes.c
>> index e6e950b7cf32..eff7d7fab535 100644
>> --- a/arch/riscv/kernel/probes/kprobes.c
>> +++ b/arch/riscv/kernel/probes/kprobes.c
>> @@ -24,12 +24,14 @@ post_kprobe_handler(struct kprobe *, struct kprobe_ctlblk *, struct pt_regs *);
>>  static void __kprobes arch_prepare_ss_slot(struct kprobe *p)
>>  {
>>  	unsigned long offset = GET_INSN_LENGTH(p->opcode);
>> +	const kprobe_opcode_t brk_insn = __BUG_INSN_32;
>> +	kprobe_opcode_t slot[MAX_INSN_SIZE];
>>  
>>  	p->ainsn.api.restore = (unsigned long)p->addr + offset;
>>  
>> -	patch_text(p->ainsn.api.insn, p->opcode);
>> -	patch_text((void *)((unsigned long)(p->ainsn.api.insn) + offset),
>> -		   __BUG_INSN_32);
>> +	memcpy(slot, &p->opcode, offset);
>> +	memcpy((void *)((unsigned long)slot + offset), &brk_insn, 4);
>> +	patch_text_nosync(p->ainsn.api.insn, slot, offset + 4);
>>  }
>>  
>>  static void __kprobes arch_prepare_simulate(struct kprobe *p)
>> -- 
>> 2.17.1
>>
>>
>> _______________________________________________
>> linux-riscv mailing list
>> linux-riscv@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-riscv
> .

-- 
BR,
Liao, Chang

  parent reply	other threads:[~2022-09-08  1:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07  2:33 Liao Chang
2022-09-07 17:21 ` Jisheng Zhang
2022-09-07 22:28   ` Masami Hiramatsu
2022-09-08  1:43   ` liaochang (A) [this message]
2022-09-08 12:49     ` Masami Hiramatsu
2022-09-09  1:55       ` liaochang (A)
2022-09-10  2:24         ` Masami Hiramatsu

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=a00328a1-47ee-3700-8cd8-1a9f4e0d7a2b@huawei.com \
    --to=liaochang1@huawei.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=jszhang@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mhiramat@kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.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

all inboxes | Powered by JetHome®