Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp336877ybn; Wed, 25 Sep 2019 00:13:47 -0700 (PDT) X-Google-Smtp-Source: APXvYqyG+g1nRG7zB7a/QO+dl8Q5ai5WfSePMQN3dpBFHmql/r6h640gaSgLb5nF0KV/nwYb3IAq X-Received: by 2002:adf:f212:: with SMTP id p18mr1402045wro.340.1569395627267; Wed, 25 Sep 2019 00:13:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569395627; cv=none; d=google.com; s=arc-20160816; b=Llnvj4mbYbCkxIg9QZznK/FOm9NRTM7v3yWB4fNaLaV8aBHfnxNl9iO82E1hNAvZbQ Q/vPbfPunyb/BaasrAO689dQQpr9yxYDQRaf7hCOf5I3/s2rHrq9UOKE6HMmbI5gPzs1 Zp6niffk4tj69KajEKFTgW6LawLr7tCqbBOeuK7rvFH0e/Q9pH5LGGjELDfRg2qw72n7 x+GednxgVHMtecwlPKGlyyGVw1FI/htXfxvixIu0aNMqUqqp3pOdXfIwCMBn07jjuuRd 5CRb9pg763BKH3dZevGsW+nHLrUwuCCgahON9RqJrbixD/9q9tPwAhLSx21iH4n53n3n v9wQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from; bh=ktu34cHEa9otJsd756sXhMbwQrS4uL8lKCTJ0M1+YIY=; b=TNLcS5L6zA4jO52fpJYr2+o4AyGcWYxEtS5zc+87OxRJ9+q5D4cK7v3jQ8SZ/2vb7O JS1sVHMJBtgSmoG0ZY2+PA4jtKMN+vTMa49cRxUju9in5thyglMZeRBYjd6t3n7L8LRh sj+KX+E3kf6nbQxNuceVSygrcMuNmp3Ai0sehA8fW99vM07Z5HazexAeqIHDamIa8ehu WGkEKfHuDbmkB2TJm9iNphlXs2z+0LHX8e7FuvlhpFV9K9VPjLOOOPnWSy9lwSrIE5KZ YLD2nlEQG/UTuQvT9wSazmWupn4mYVkbg7MFXWUaorfa5zOxM0L+1zWJ42rZol8r7uBT VG9g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b3si2803562ede.118.2019.09.25.00.13.12; Wed, 25 Sep 2019 00:13:47 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2405474AbfIWHyO (ORCPT + 99 others); Mon, 23 Sep 2019 03:54:14 -0400 Received: from mx2.suse.de ([195.135.220.15]:54698 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2404826AbfIWHyO (ORCPT ); Mon, 23 Sep 2019 03:54:14 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 4FB45B150; Mon, 23 Sep 2019 07:54:12 +0000 (UTC) From: Michal Suchanek To: linuxppc-dev@lists.ozlabs.org Cc: Michal Suchanek , Benjamin Herrenschmidt , Paul Mackerras , Michael Ellerman , Hari Bathini , Mahesh Salgaonkar , linux-kernel@vger.kernel.org Subject: [PATCH v2 rebased] powerpc/fadump: when fadump is supported register the fadump sysfs files. Date: Mon, 23 Sep 2019 09:54:06 +0200 Message-Id: <20190923075406.5854-1-msuchanek@suse.de> X-Mailer: git-send-email 2.23.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Currently it is not possible to distinguish the case when fadump is supported by firmware and disabled in kernel and completely unsupported using the kernel sysfs interface. User can investigate the devicetree but it is more reasonable to provide sysfs files in case we get some fadumpv2 in the future. With this patch sysfs files are available whenever fadump is supported by firmware. Signed-off-by: Michal Suchanek Acked-by: Hari Bathini --- v2: move the sysfs initialization earlier to avoid condition nesting rebase: on top of the powernv fadump support --- arch/powerpc/kernel/fadump.c | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/arch/powerpc/kernel/fadump.c b/arch/powerpc/kernel/fadump.c index ed59855430b9..cdcdea6c6453 100644 --- a/arch/powerpc/kernel/fadump.c +++ b/arch/powerpc/kernel/fadump.c @@ -1466,16 +1466,20 @@ static void fadump_init_files(void) */ int __init setup_fadump(void) { - if (!fw_dump.fadump_enabled) - return 0; - - if (!fw_dump.fadump_supported) { + if (!fw_dump.fadump_supported && fw_dump.fadump_enabled) { printk(KERN_ERR "Firmware-assisted dump is not supported on" " this hardware\n"); - return 0; } + if (!fw_dump.fadump_supported) + return 0; + + fadump_init_files(); fadump_show_config(); + + if (!fw_dump.fadump_enabled) + return 1; + /* * If dump data is available then see if it is valid and prepare for * saving it to the disk. @@ -1492,8 +1496,6 @@ int __init setup_fadump(void) else if (fw_dump.reserve_dump_area_size) fw_dump.ops->fadump_init_mem_struct(&fw_dump); - fadump_init_files(); - return 1; } subsys_initcall(setup_fadump); -- 2.23.0