Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp276298rwb; Mon, 26 Sep 2022 18:50:37 -0700 (PDT) X-Google-Smtp-Source: AMsMyM7sYUs178CoPzd19R8ZJT9ZaqoAC5mv+rp3KAX5miZZcIHpb4SZHctA5nXYhDsscqLynTwB X-Received: by 2002:a17:907:6ea1:b0:783:cc69:342 with SMTP id sh33-20020a1709076ea100b00783cc690342mr3701920ejc.97.1664243437598; Mon, 26 Sep 2022 18:50:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1664243437; cv=none; d=google.com; s=arc-20160816; b=Na23UosoAzP2vrLPoGkqnerMR5GSfmW1YMckir+tMi0TZ/YJIW5bUVYDpPA+88Z1WK MH/SxG89xkkdhdfVd//+C/pIxl1k6w3rp5/upFpzFZ3hwhlv6tYhbfll8JNO/ajL/6yB jo2tvDZDLHzgTSrm9KCfrOSg17R5L08TfBcFmsUQvOQXAXQtoPbqNAU2VCsULciEyO52 w3fbM58rtuugXEYt/BuZwJykXKepRm9Iwuly4C4gxcR9KS/wdoDgvRB/LRHe7AJsnwXl HJ+c6s2mFs3ZRaOAnIR8jyc65agkZ6Th1AisnOvbMW2KL4GQQK7u7TDyxhCcb9ru9hed +BVQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:subject:user-agent:mime-version:date:message-id; bh=RdYqVMI0b+MSOBbh1DkEDQlzsCwmQ/79hklfZeI67gk=; b=kL581gGcHEEPLI9fhDZZoBgBG5T5XD+zfZ5EzGPEPPFUFw1gDkh/bLq23QrkGs7IGh I+dRv6p89GyqGmA/+NKg55tbZp9rip797fDAxhZZzbxb3b54OgGPj+cLbOF4Eu6kIRos AMUuD+AzRwbXB50hDAQl1zv95VctAes/6ZsycvKx0lGoI2N2RlVx+vPvrR+/DxdDi/Ry Bw0VGjGyxxrMSle3B72SFqiJDeqNZvK+v0ALtOMJIG3e2BsNdLz8hQonJk2Cgt6Rbp5r hEgDbMXJpwwQsBJ192mAm6dzalnTFnV9SAFE4BFXVaSVs4eSwhCfbFr0FYbMgSfL7/Cf gzoQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id cw8-20020a170906478800b0078334ccc570si1534688ejc.328.2022.09.26.18.50.10; Mon, 26 Sep 2022 18:50:37 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229946AbiI0Bhn (ORCPT + 99 others); Mon, 26 Sep 2022 21:37:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44430 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229724AbiI0Bhk (ORCPT ); Mon, 26 Sep 2022 21:37:40 -0400 Received: from szxga08-in.huawei.com (szxga08-in.huawei.com [45.249.212.255]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 006EA65244; Mon, 26 Sep 2022 18:37:38 -0700 (PDT) Received: from kwepemi500012.china.huawei.com (unknown [172.30.72.54]) by szxga08-in.huawei.com (SkyGuard) with ESMTP id 4Mc2FZ4cb7z1P6r6; Tue, 27 Sep 2022 09:33:22 +0800 (CST) Received: from [10.67.110.108] (10.67.110.108) by kwepemi500012.china.huawei.com (7.221.188.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Tue, 27 Sep 2022 09:37:36 +0800 Message-ID: Date: Tue, 27 Sep 2022 09:37:35 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.4.0 Subject: Re: [PATCH 3/3] arm64/kprobe: Optimize the performance of patching single-step slot To: "Masami Hiramatsu (Google)" CC: Mark Rutland , , , , , , , , , , , , , References: <20220923084658.99304-1-liaochang1@huawei.com> <20220923084658.99304-4-liaochang1@huawei.com> <19ffdae6-8484-08e5-f408-ab39a97ce5c0@huawei.com> <20220925102159.639f39818672ef60a4ddc7f1@kernel.org> From: "liaochang (A)" In-Reply-To: <20220925102159.639f39818672ef60a4ddc7f1@kernel.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Originating-IP: [10.67.110.108] X-ClientProxiedBy: dggems702-chm.china.huawei.com (10.3.19.179) To kwepemi500012.china.huawei.com (7.221.188.12) X-CFilter-Loop: Reflected X-Spam-Status: No, score=-6.5 required=5.0 tests=BAYES_00,NICE_REPLY_A, RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 在 2022/9/25 9:21, Masami Hiramatsu (Google) 写道: > On Sat, 24 Sep 2022 09:52:28 +0800 > "liaochang (A)" wrote: > >> >> >> 在 2022/9/23 20:39, Mark Rutland 写道: >>> On Fri, Sep 23, 2022 at 04:46:58PM +0800, Liao Chang wrote: >>>> Single-step slot would not be used until kprobe is enabled, that means >>>> no race condition occurs on it under SMP, hence it is safe to pacth ss >>>> slot without stopping machine. >>> >>> I think this is correct, but this depends on a couple of subtleties, >>> importantly: >>> >>> * That the I-cache maintenance for these instructions is complete *before* the >>> kprobe BRK is written (and aarch64_insn_patch_text_nosync() ensures this, but >>> just omits causing a Context-Synchronization-Event on all CPUS). >> >> So in order to guarantee the I-cache maintenance is observed on all CPUS, >> it needs to be followed by a explicit Context-Synchronization-Event, perhaps >> it is better to place ISB before kprobe BRK is written. >> >>> >>> * That the kprobe BRK results in an exception (and consequently a >>> Context-Synchronoization-Event), which ensures that the CPU will fetch the >>> single-step slot instructions *after* this, ensuring that the new >>> instructions are used. >> >> Yes, because of single-step slot is installed int the BRK execption handler, >> so it is not necessary to generate Context-Synchronization-Event via ISB mentioned above... > > Can you update the patch including above as comments in the code? > Maybe you also have to ensure it on other patches too. OK,i will add these comments in the code. Thanks. > > Thank you, > >> >> Thanks. >> >>> >>> It would be good if we could call that out explicitly. >>> >>> Thanks, >>> Mark. >>> >>>> Since I and D caches are coherent within single-step slot from >>>> aarch64_insn_patch_text_nosync(), hence no need to do it again via >>>> flush_icache_range(). >>>> >>>> Acked-by: Masami Hiramatsu (Google) >>>> Signed-off-by: Liao Chang >>>> --- >>>> arch/arm64/kernel/probes/kprobes.c | 7 ++----- >>>> 1 file changed, 2 insertions(+), 5 deletions(-) >>>> >>>> diff --git a/arch/arm64/kernel/probes/kprobes.c b/arch/arm64/kernel/probes/kprobes.c >>>> index d1d182320245..29b98bc12833 100644 >>>> --- a/arch/arm64/kernel/probes/kprobes.c >>>> +++ b/arch/arm64/kernel/probes/kprobes.c >>>> @@ -44,13 +44,10 @@ post_kprobe_handler(struct kprobe *, struct kprobe_ctlblk *, struct pt_regs *); >>>> static void __kprobes arch_prepare_ss_slot(struct kprobe *p) >>>> { >>>> kprobe_opcode_t *addr = p->ainsn.api.insn; >>>> - void *addrs[] = {addr, addr + 1}; >>>> - u32 insns[] = {p->opcode, BRK64_OPCODE_KPROBES_SS}; >>>> >>>> /* prepare insn slot */ >>>> - aarch64_insn_patch_text(addrs, insns, 2); >>>> - >>>> - flush_icache_range((uintptr_t)addr, (uintptr_t)(addr + MAX_INSN_SIZE)); >>>> + aarch64_insn_patch_text_nosync(addr, p->opcode); >>>> + aarch64_insn_patch_text_nosync(addr + 1, BRK64_OPCODE_KPROBES_SS); >>>> >>>> /* >>>> * Needs restoring of return address after stepping xol. >>>> -- >>>> 2.17.1 >>>> >>> >>> . >> >> -- >> BR, >> Liao, Chang > > -- BR, Liao, Chang