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=-4.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_GIT 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 37F0CC4CEC7 for ; Sun, 15 Sep 2019 13:23:23 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 16D4F214C6 for ; Sun, 15 Sep 2019 13:23:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730047AbfIONXV (ORCPT ); Sun, 15 Sep 2019 09:23:21 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:39076 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726268AbfIONXV (ORCPT ); Sun, 15 Sep 2019 09:23:21 -0400 Received: from pps.filterd (m0098417.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x8FDMb47082406 for ; Sun, 15 Sep 2019 09:23:19 -0400 Received: from e06smtp01.uk.ibm.com (e06smtp01.uk.ibm.com [195.75.94.97]) by mx0a-001b2d01.pphosted.com with ESMTP id 2v1dk4sqxd-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Sun, 15 Sep 2019 09:23:19 -0400 Received: from localhost by e06smtp01.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Sun, 15 Sep 2019 14:23:17 +0100 Received: from b06cxnps3074.portsmouth.uk.ibm.com (9.149.109.194) by e06smtp01.uk.ibm.com (192.168.101.131) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Sun, 15 Sep 2019 14:23:16 +0100 Received: from b06wcsmtp001.portsmouth.uk.ibm.com (b06wcsmtp001.portsmouth.uk.ibm.com [9.149.105.160]) by b06cxnps3074.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id x8FDNF4t56950890 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sun, 15 Sep 2019 13:23:15 GMT Received: from b06wcsmtp001.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 2FF20A405C; Sun, 15 Sep 2019 13:23:15 +0000 (GMT) Received: from b06wcsmtp001.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 6D4FCA405F; Sun, 15 Sep 2019 13:23:13 +0000 (GMT) Received: from localhost.localdomain.com (unknown [9.199.54.91]) by b06wcsmtp001.portsmouth.uk.ibm.com (Postfix) with ESMTP; Sun, 15 Sep 2019 13:23:13 +0000 (GMT) From: Sourabh Jain To: linuxppc-dev@ozlabs.org Cc: mahesh@linux.vnet.ibm.com, hbathini@linux.ibm.com, linux-kernel@vger.kernel.org, mpe@ellerman.id.au, corbet@lwn.net, linux-doc@vger.kernel.org Subject: [PATCH 0/4] reorganize and add FADump sysfs files Date: Sun, 15 Sep 2019 18:53:06 +0530 X-Mailer: git-send-email 2.17.2 X-TM-AS-GCONF: 00 x-cbid: 19091513-4275-0000-0000-00000366642A X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19091513-4276-0000-0000-00003878C3F5 Message-Id: <20190915132310.13542-1-sourabhjain@linux.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-09-15_07:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=948 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1908290000 definitions=main-1909150147 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Currently, the FADump sysfs files are present inside /sys/kernel directory. But as the number of FADump sysfs file increases it is not a good idea to push all of them in /sys/kernel directory. It is better to have separate directory to keep all the FADump sysfs files. The patch series reorganizes the FADump sysfs files and avail all the existing FADump sysfs files present inside /sys/kernel into a new directory named fadump. Currently, all the FADump sysfs files are replicated into a new directory to maintain the backward compatibility and will eventually get removed in future. In addition to this a new FADump sys interface is added to get the amount of memory reserved by FADump for saving the crash dump. The series applies on top of: https://lists.ozlabs.org/pipermail/linuxppc-dev/2019-September/196871.html Sourabh Jain (4): powerpc/fadump: replicate /sys/kernel/fadump_* sysfs into /sys/kernel/fadump/ Documentation/ABI: add ABI documentation for /sys/kernel/fadump_* Documentation/ABI: mark /sys/kernel/fadump_* sysfs files deprecated powerpc/fadump: sysfs for fadump memory reservation .../ABI/obsolete/sysfs-kernel-fadump_enabled | 10 ++++ .../obsolete/sysfs-kernel-fadump_registered | 11 +++++ .../obsolete/sysfs-kernel-fadump_release_mem | 11 +++++ .../sysfs-kernel-fadump_release_opalcore | 10 ++++ Documentation/ABI/testing/sysfs-kernel-fadump | 48 +++++++++++++++++++ .../powerpc/firmware-assisted-dump.rst | 14 ++++++ arch/powerpc/kernel/fadump.c | 43 +++++++++++++++++ arch/powerpc/platforms/powernv/opal-core.c | 7 +++ 8 files changed, 154 insertions(+) create mode 100644 Documentation/ABI/obsolete/sysfs-kernel-fadump_enabled create mode 100644 Documentation/ABI/obsolete/sysfs-kernel-fadump_registered create mode 100644 Documentation/ABI/obsolete/sysfs-kernel-fadump_release_mem create mode 100644 Documentation/ABI/obsolete/sysfs-kernel-fadump_release_opalcore create mode 100644 Documentation/ABI/testing/sysfs-kernel-fadump -- 2.17.2