Received: by 2002:a05:6358:4e97:b0:b3:742d:4702 with SMTP id ce23csp1278588rwb; Thu, 11 Aug 2022 20:26:46 -0700 (PDT) X-Google-Smtp-Source: AA6agR7KbzHONmr1jWD0KXmtV30uU2qNwnGFWA1sGK/rBGxp29Lbsziz5cdRo/WSWR/t5MimZ8M2 X-Received: by 2002:a63:97:0:b0:420:f9b7:a443 with SMTP id 145-20020a630097000000b00420f9b7a443mr1658495pga.234.1660274806648; Thu, 11 Aug 2022 20:26:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1660274806; cv=none; d=google.com; s=arc-20160816; b=VGyubonYd8cbdDrWF+S0duX80fhCRl7M86d7BOevtPagpBRmpLllUz0RLi9G9UOb9L DRBT2YfD7HTasfhU+pVdipc36KnpRWJHjx9X2ufFOHAO2e6omjnVELjc309sE4+pSUB2 O18R2BdtbrNqfwVUpmuR2zZejX3w4bt/aNvhE+lG5mimU4UO7e/j7dxC/VSgPc7s2p2+ vGcJfLEVx754HKMggHEQUBD0BwdSesMXZLpWrMCTwzLzVJ85olm6XHeK9VFnnEoc7E9B 9NVpwsY6SQDqwvhQg7J8yrkvxdaDX/CtDKAWL25AVsCmfNqkWpeglCVV2B5ou/YsHREs mjJA== 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 :mime-version:user-agent:date:message-id:from:references:cc:to :subject; bh=gacwWvcNO57vkFh4AJHK9UfN54y4D1WJ5DnfouaeKSY=; b=BN99KCVTTpRSRMUWchMBYwGxA25sXm1CBY3mNcxCwZQZismrnsk30CYAqo8uU4vs6U zNxmkCqffnusDr7OYLqKnoSlve9x8IhuKSIHCb1RvEuiBrjG6Bi7wcUS5YDZrvAPgMJB B8m16NYKuQV3QjJmUr7A5hxsU7kCodI7Nm2F2VZ04CrkJGCTHlJ9wWYKgUESSVDZvWsN hzOR5gO4jAlVmCf1KXWZEapbsn1sXCF8bKQGZdRJQuEWsGlp1GwLZEoqZRkATfA4ADrG m/SbBcV36c4amxnWDjkwn1JQ37AG6dDOejCkqJx/BfUXs30xj37Kn8vNN2LsoOs5iXR1 9pSw== 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=NONE sp=NONE dis=NONE) header.from=alibaba.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id bc2-20020a170902930200b0016ecd3d0519si912362plb.593.2022.08.11.20.26.33; Thu, 11 Aug 2022 20:26:46 -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=NONE sp=NONE dis=NONE) header.from=alibaba.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236896AbiHLDYw (ORCPT + 99 others); Thu, 11 Aug 2022 23:24:52 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52796 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237085AbiHLDYT (ORCPT ); Thu, 11 Aug 2022 23:24:19 -0400 Received: from out199-9.us.a.mail.aliyun.com (out199-9.us.a.mail.aliyun.com [47.90.199.9]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8F667A3D44; Thu, 11 Aug 2022 20:23:52 -0700 (PDT) X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R151e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=ay29a033018046051;MF=xianting.tian@linux.alibaba.com;NM=1;PH=DS;RN=22;SR=0;TI=SMTPD_---0VM04yDW_1660274624; Received: from B-LB6YLVDL-0141.local(mailfrom:xianting.tian@linux.alibaba.com fp:SMTPD_---0VM04yDW_1660274624) by smtp.aliyun-inc.com; Fri, 12 Aug 2022 11:23:45 +0800 Subject: Re: [PATCH V6 0/6] RISC-V fixups to work with crash tool To: Palmer Dabbelt , Conor.Dooley@microchip.com Cc: Paul Walmsley , aou@eecs.berkeley.edu, anup@brainfault.org, heiko@sntech.de, guoren@kernel.org, mick@ics.forth.gr, alexandre.ghiti@canonical.com, bhe@redhat.com, vgoyal@redhat.com, dyoung@redhat.com, corbet@lwn.net, Conor.Dooley@microchip.com, kexec@lists.infradead.org, linux-doc@vger.kernel.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, crash-utility@redhat.com, heinrich.schuchardt@canonical.com, k-hagio-ab@nec.com, hschauhan@nulltrace.org, yixun.lan@gmail.com References: From: Xianting Tian Message-ID: Date: Fri, 12 Aug 2022 11:23:43 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-9.9 required=5.0 tests=BAYES_00, ENV_AND_HDR_SPF_MATCH,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE,UNPARSEABLE_RELAY,USER_IN_DEF_SPF_WL 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/8/12 上午12:17, Palmer Dabbelt 写道: > On Thu, 11 Aug 2022 00:41:44 PDT (-0700), > xianting.tian@linux.alibaba.com wrote: >> I ever sent the patch 1 in the link: >> https://patchwork.kernel.org/project/linux-riscv/patch/20220708073150.352830-3-xianting.tian@linux.alibaba.com/ >> >> And patch 2,3 in the link: >> https://patchwork.kernel.org/project/linux-riscv/patch/20220714113300.367854-2-xianting.tian@linux.alibaba.com/ >> >> https://patchwork.kernel.org/project/linux-riscv/patch/20220714113300.367854-3-xianting.tian@linux.alibaba.com/ >> >> >> This patch set just put these patches together, and with three new >> patch 4, 5, 6. >> these six patches are the fixups for machine_kexec, kernel mode PC >> for vmcore >> and improvements for vmcoreinfo, memory layout dump and fixup >> schedule out issue >> in machine_crash_shutdown(). >> >> The main changes in the six patchs as below, >> Patch 1: Fixup use of smp_processor_id() in preemptible context, to >> cleanup >>          the console prints. >> Patch 2: Fixup to get correct kernel mode PC for kernel mode regs for >> vmcore. >> Patch 3: Fixup schedule out issue in machine_crash_shutdown() >> Patch 4: Add modules to virtual kernel memory layout dump. >> Patch 5: Add VM layout, va bits, ram base to vmcoreinfo, which can >> simplify >>          the development of crash tool as ARM64 already did >>          (arch/arm64/kernel/crash_core.c). >> Patch 6: Updates vmcoreinfo.rst for vmcoreinfo export for RISCV64. >> >> With these six patches(patch 2 is must), crash tool can work well to >> analyze >> a vmcore. The patches for crash tool for RISCV64 is in the link: >> https://lore.kernel.org/linux-riscv/20220801043040.2003264-1-xianting.tian@linux.alibaba.com/ >> >> >> ------ >> Changes v1 -> v2: >>   1, remove the patch "Add a fast call path of crash_kexec()" from >> this series >>      of patches, as it already applied to riscv git. >> https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/commit/?h=for-next&id=3f1901110a89b0e2e13adb2ac8d1a7102879ea98 >>   2, add 'Reviewed-by' based on the comments of v1. >> Changes v2 -> v3: >>   use "riscv" instead of "riscv64" in patch 5 subject line. >> Changes v3 -> v4: >>   use "riscv" instead of "riscv64" in the summary of patch 5 subject >> line. >> Changes v4 -> v5: >>   add a new patch "RISC-V: Fixup schedule out issue in >> machine_crash_shutdown()" >> Changes v5 -> v6: >>   1, move "fixup" patches to the start of the patch set. >>   2, change patch 1, 2, 6's subject to make it tell more what it's >> about. >>   3, add Fixes for patch 3. >>   4, adjuest the changes format for patch 6. >> >> >> Xianting Tian (6): >>   RISC-V: kexec: Fixup use of smp_processor_id() in preemptible context >>   RISC-V: Fixup get incorrect user mode PC for kernel mode regs >>   RISC-V: Fixup schedule out issue in machine_crash_shutdown() >>   RISC-V: Add modules to virtual kernel memory layout dump >>   RISC-V: Add arch_crash_save_vmcoreinfo support >>   Documentation: kdump: describe VMCOREINFO export for RISCV64 >> >>  .../admin-guide/kdump/vmcoreinfo.rst          | 31 +++++++++++++++++++ >>  arch/riscv/kernel/Makefile                    |  1 + >>  arch/riscv/kernel/crash_core.c                | 29 +++++++++++++++++ >>  arch/riscv/kernel/crash_save_regs.S           |  2 +- >>  arch/riscv/kernel/machine_kexec.c             | 28 ++++++++++++++--- >>  arch/riscv/mm/init.c                          |  4 +++ >>  6 files changed, 89 insertions(+), 6 deletions(-) >>  create mode 100644 arch/riscv/kernel/crash_core.c > > Thank.  I've taken the first 4 onto for-next, which is still targeted > for 5.20, as they're fixes.  I'm not opposed to taking the > documentation patch for this cycle as well, it just needs some > going-over as the wording looks very odd (or at least it does to me > right now, maybe I'm just still half asleep).  Patch 5 is a new > feature, and given that it's being spun during the merge window it's > too late. Thank you Palmer, Conor. I saw patch 5,6 already merged to Palmer's riscv-crash branch, https://git.kernel.org/pub/scm/linux/kernel/git/palmer/linux.git/log/?h=riscv-crash Looking forward to be merged to 6.1(?). thanks.