Received: by 2002:ac0:e34a:0:0:0:0:0 with SMTP id g10csp532610imn; Tue, 26 Jul 2022 02:39:05 -0700 (PDT) X-Google-Smtp-Source: AGRyM1tQTo4M+vHVrZqQZA21T+7VKMIDZzd30TOLHPB696fHPzMz4+PVSrMTwwBaUDUi7rD1gQXi X-Received: by 2002:a17:907:720e:b0:72b:9cfe:21da with SMTP id dr14-20020a170907720e00b0072b9cfe21damr12505165ejc.575.1658828344829; Tue, 26 Jul 2022 02:39:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1658828344; cv=none; d=google.com; s=arc-20160816; b=grgk/ADcdhGhNWO3/HAFlPGNl3W3Vc9Oy0EdNLmNXPc3jKUoT1cn1Z/2hgeVFo5eTl Zmv642PejUI4cskDyMMQvsGmHb/EIVut+n+en6hsx5KVb4nzN24j11POvvnIlqdXbvQZ +LYgeQcLgr5syBqVgoyJarJSAMDPOFpsN3YbKJ60gn/6AdCJeGegqrUMOFyYvq3l6olr QvcNYeDiBTj3VlK6bZvFTxiSMbe1u60szRdXQ9iwfW1FmFfmtF6yubE3dLmpskgANUiX zCOPYJ9DrfzFyQZIuLzcuLWzWRnQaBfi7QxDtdYHmM3wpr6OE9vy6Tr/6VgeLEAdc+k4 +PfQ== 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:references:cc:to:from :subject; bh=6yul3tAZD7W3H9lV71v6Bm81Mt7mxJa/3SvZI3BIknA=; b=RvaODKCBG/qGf7NXZiZYUs4uX0vLpJ+rnGKMWJO8qfC0fT4zyuodk8XBTG8ZVD1oxz nxevGSmUeeOAfrnRWrLJfNVDVDPdE/TVlCOGO6ims1EzkK/EWaC2ztq0xbfvRqOvDPUl q089h13XKPyxM9b767DZgartsR4Bd28miqxFNXeihJ01RvDi/C9EH72bTXE8xGNEedS2 0BO+qI76HF7YmLRlgfXqM2XmdcvwKcjMMt+06yrEEJSxoZieGBmzcqB/Kou1besJM7aE iA4fzfuM+yWFidxBhyzPjQam4kyxkkh75j391/Dizgt6j0FH6WYb2Qevxl9tub9fmD51 PPVQ== 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 i21-20020a05640242d500b0043a4cff7e3csi9934670edc.423.2022.07.26.02.38.40; Tue, 26 Jul 2022 02:39:04 -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 S237991AbiGZJ2r (ORCPT + 99 others); Tue, 26 Jul 2022 05:28:47 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34162 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229746AbiGZJ2p (ORCPT ); Tue, 26 Jul 2022 05:28:45 -0400 Received: from out30-43.freemail.mail.aliyun.com (out30-43.freemail.mail.aliyun.com [115.124.30.43]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 716FF2ED77; Tue, 26 Jul 2022 02:28:43 -0700 (PDT) X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R191e4;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_---0VKUwbzM_1658827715; Received: from B-LB6YLVDL-0141.local(mailfrom:xianting.tian@linux.alibaba.com fp:SMTPD_---0VKUwbzM_1658827715) by smtp.aliyun-inc.com; Tue, 26 Jul 2022 17:28:37 +0800 Subject: Re: [RESEND PATCH V2 0/5] Fixups to work with crash tool From: Xianting Tian To: Conor.Dooley@microchip.com Cc: alexandre.ghiti@canonical.com, heiko@sntech.de, palmer@dabbelt.com, mick@ics.forth.gr, guoren@kernel.org, kexec@lists.infradead.org, bhe@redhat.com, linux-doc@vger.kernel.org, vgoyal@redhat.com, linux-riscv@lists.infradead.org, dyoung@redhat.com, linux-kernel@vger.kernel.org, crash-utility@redhat.com, huanyi.xj@alibaba-inc.com, heinrich.schuchardt@canonical.com, anup@brainfault.org, corbet@lwn.net, k-hagio-ab@nec.com, hschauhan@nulltrace.org, paul.walmsley@sifive.com, aou@eecs.berkeley.edu References: <20220725014539.1037627-1-xianting.tian@linux.alibaba.com> <51c97da7-422f-1b5b-03d3-dc36c9132c2a@microchip.com> <7a395f64-8ec7-e07f-e763-afc1f2611c75@linux.alibaba.com> <2301681f-361d-b85b-e255-3bf449ceeaa9@microchip.com> Message-ID: <6320e6dd-ebd9-3575-a85f-c3a2f92e9f54@linux.alibaba.com> Date: Tue, 26 Jul 2022 17:28:35 +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,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS,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/7/26 下午4:16, Xianting Tian 写道: > > 在 2022/7/26 下午4:01, Conor.Dooley@microchip.com 写道: >> On 26/07/2022 08:54, tianxianting wrote: >>> 在 2022/7/26 上午1:13, Conor.Dooley@microchip.com 写道: >>>> That said, this does not apply to riscv/for-next: >>>> b4 shazam 20220725014539.1037627-1-xianting.tian@linux.alibaba.com >>>> Grabbing thread from >>>> lore.kernel.org/all/20220725014539.1037627-1-xianting.tian%40linux.alibaba.com/t.mbox.gz >>>> Checking for newer revisions on https://lore.kernel.org/all/ >>>> Analyzing 6 messages in the thread >>>> Checking attestation on all messages, may take a moment... >>>> --- >>>>     [PATCH v2 1/5] RISC-V: use __smp_processor_id() instead of >>>> smp_processor_id() >>>>     [PATCH v2 2/5] RISC-V: Add arch_crash_save_vmcoreinfo support >>>>     [PATCH v2 3/5] riscv: Add modules to virtual kernel memory >>>> layout dump >>>>     [PATCH v2 4/5] RISC-V: Fixup getting correct current pc >>>>     [PATCH v2 5/5] riscv: crash_core: Export kernel vm layout, >>>> phys_ram_base >>>> --- >>>> Total patches: 5 >>>> --- >>>> Applying: RISC-V: use __smp_processor_id() instead of >>>> smp_processor_id() >>>> Applying: RISC-V: Add arch_crash_save_vmcoreinfo support >>>> Patch failed at 0002 RISC-V: Add arch_crash_save_vmcoreinfo support >>> patch 2 apply is OK for me, I don't know why you failed :( >>> Do you have more detals for this? >>> >> What did you apply it to? It does not apply for me to riscv/for-next: >> https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/log/?h=for-next >> > > This 5 patches are based on the master branch of below git: > > https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux.git > > > "git am 0002-RISC-V-Add-arch_crash_save_vmcoreinfo-support.patch" to > this git is ok for me. > > All is correct? I figured out the reason, there is one difference in arch/riscv/kernel/Makefile between riscv/for-next and torvalds/linux. For riscv/for-next, in line 81 of arch/riscv/kernel/Makefile, it is:     obj-$(CONFIG_KEXEC)        += kexec_relocate.o crash_save_regs.o machine_kexec.o But for torvalds/linux, in line 81 of arch/riscv/kernel/Makefile, it is:     obj-$(CONFIG_KEXEC_CORE)        += kexec_relocate.o crash_save_regs.o machine_kexec.o torvalds/linux is newer than riscv/for-next,  commit 3a66a08759 ("RISC-V: kexec: Fix build error without CONFIG_KEXEC") added "CONFIG_KEXEC_CORE" for torvalds/linux, But riscv/for-next doesn't contain the commit. > >> >> Thanks, >> Conor. >>