From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B53C2C433E9 for ; Fri, 22 Jan 2021 01:25:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 65EFB23A56 for ; Fri, 22 Jan 2021 01:25:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726166AbhAVBYv (ORCPT ); Thu, 21 Jan 2021 20:24:51 -0500 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:37438 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725863AbhAVBYs (ORCPT ); Thu, 21 Jan 2021 20:24:48 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1611278598; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=SJoWL2veJ5k/D7xEL6G5+QjIu4GFUmt+PwMfZPwuV6Y=; b=SSqEl+Hc485o/7oY4Lbn9lUTA8oENiijWsxEF0qTHs7L5YhefnUetOFHINPOL4viEnR/0o CYzA5AuIkYEaS6nBoZRaotQHaXCZodxXoc0J/OvkzI/BcYiTgiFUnDbv+C9fy9FO9NsN54 dfghHH9gZEgH9LOIdeShIqR/5htaPmk= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-330-CGjKzgi4OAeR7HI75U9w6g-1; Thu, 21 Jan 2021 20:23:16 -0500 X-MC-Unique: CGjKzgi4OAeR7HI75U9w6g-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 901BC8145E1; Fri, 22 Jan 2021 01:23:12 +0000 (UTC) Received: from dhcp-128-65.nay.redhat.com (ovpn-12-255.pek2.redhat.com [10.72.12.255]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 847B760BF3; Fri, 22 Jan 2021 01:22:58 +0000 (UTC) Date: Fri, 22 Jan 2021 09:22:54 +0800 From: Dave Young To: john.p.donnelly@oracle.com Cc: Guilherme Piccoli , Kairui Song , Saeed Mirzamohammadi , Geert Uytterhoeven , linux-doc@vger.kernel.org, Catalin Marinas , Bjorn Andersson , "H. Peter Anvin" , Will Deacon , Anson Huang , Jonathan Corbet , the arch/x86 maintainers , Michael Walle , Krzysztof Kozlowski , Ingo Molnar , Vivek Goyal , Arnd Bergmann , Borislav Petkov , Thomas Gleixner , linux-arm-kernel@lists.infradead.org, Baoquan He , "Martin K. Petersen" , Randy Dunlap , kexec mailing list , Linux Kernel Mailing List , "# v4 . 16+" , Li Yang , Miguel Ojeda , Vinod Koul , Diego Elio =?iso-8859-1?Q?Petten=F2?= , Olof Johansson , Shawn Guo Subject: Re: [PATCH 1/1] kernel/crash_core.c - Add crashkernel=auto for x86 and ARM Message-ID: <20210122012254.GA3174@dhcp-128-65.nay.redhat.com> References: <20201118232431.21832-1-saeed.mirzamohammadi@oracle.com> <20201123034705.GA5908@dhcp-128-65.nay.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi John, On 01/21/21 at 09:32am, john.p.donnelly@oracle.com wrote: > On 11/22/20 9:47 PM, Dave Young wrote: > > Hi Guilherme, > > On 11/22/20 at 12:32pm, Guilherme Piccoli wrote: > > > Hi Dave and Kairui, thanks for your responses! OK, if that makes sense > > > to you I'm fine with it. I'd just recommend to test recent kernels in > > > multiple distros with the minimum "range" to see if 64M is enough for > > > crashkernel, maybe we'd need to bump that. > > > > Giving the different kernel configs and the different userspace > > initramfs setup it is hard to get an uniform value for all distributions, > > but we can have an interface/kconfig-option for them to provide a value like this patch > > is doing. And it could be improved like Kairui said about some known > > kernel added extra values later, probably some more improvements if > > doable. > > > > Thanks > > Dave > > > > Hi. > > Are we going to move forward with implementing this for X86 and Arm ? > > If other platform maintainers want to include this CONFIG option in their > configuration settings they have a starting point. I would expect this become arch independent. Saeed, Kairui, would any of you like to update the patch? > > Thank you, > > John. > > ( I am not currently on many of the included dist lists in this email, so > hopefully key contributors are included in this exchange ) > Thanks Dave