Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp206400img; Tue, 19 Mar 2019 22:10:41 -0700 (PDT) X-Google-Smtp-Source: APXvYqyFuygdDlwP96vl3P6OM/BAJx+/DAGQZZXQt4Y1r1oT/lHjzjcxMr0L/S5FdpgZ/39jXxOZ X-Received: by 2002:a62:4610:: with SMTP id t16mr826902pfa.217.1553058641593; Tue, 19 Mar 2019 22:10:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553058641; cv=none; d=google.com; s=arc-20160816; b=vN1DpptB0h6CYJPfAgxer8S1pmb2Vpyq/AfRdbV3oyNldM1pvyEiB/f6Zm2hKswbM+ kF6fQwCBttmVICVjUJtl2HbSsav3COPHg69HLGUeZFSxp0p/mMhdmoXHujEJllqU2zUO QxehMiqHvj4BeEIquI1mBNPg8CRhTh1UWDTxnI5CgpzTQrN/60BVxx9Z12GWEtfUUVCW RLpWUjPb+Z5+5oH7mSI63ge6KdXI7czHXixCldFg/PNXldIMY/8MyJ+Be5CRofAV1745 w+ljDRNAPmNcgdbiL+Zld3soa3WGVtRdBNES1Lbd3mnhWywk27bTK+TEDEewWJ8djIu6 TkdQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from; bh=zRNsdf+V/AK4P0Z2aSwS4lRRtyqJz6mWGX6inLxUzcw=; b=a8TblphgnYk42vZvalIJwImh/7hUawS3uacF/jBrZpS1w0LPz64aMLUu9HcqoJptCQ bgTCikOF4yax/7ItFN3uA6dgOnz53u9gH9bYshe80gDvQLh0dFhoj/9Rze4zyWMV8rId hYJ7fdEXYONKXoXS/kiCf7OChNr3JGi2/9ZpI4kIwqO9g3ceZ4bj0+cK1XE6Yqp4Ah6M W+6mROW3uJDV84s1/cExEuu8EBqbS36/cb0c15zuqGp1aRiCPSm1Fmz79NsHd2C4aWop +nI3W2naDFGfmgNTvyUG+GUc9aXbRvMa0sH83BFgq8rcbyx0fV1U+GxkPzyjGJCVfYJu MyOw== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m10si792155pgk.386.2019.03.19.22.10.26; Tue, 19 Mar 2019 22:10:41 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726152AbfCTFJp (ORCPT + 99 others); Wed, 20 Mar 2019 01:09:45 -0400 Received: from mail-pf1-f195.google.com ([209.85.210.195]:34514 "EHLO mail-pf1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725986AbfCTFJp (ORCPT ); Wed, 20 Mar 2019 01:09:45 -0400 Received: by mail-pf1-f195.google.com with SMTP id v64so1037793pfb.1 for ; Tue, 19 Mar 2019 22:09:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id; bh=zRNsdf+V/AK4P0Z2aSwS4lRRtyqJz6mWGX6inLxUzcw=; b=dXn3OpVA+JwYevRmwxKsasjxmmX1X1AYutU/a3mFKMF00ytKxwXgR+Z6P8vBeXfQpv fnt+JtyroNJby6Oj6TmbG2Fz7dtNDFnpx0x+m1Dm9Y/LbpUsysVv+fmB7pAxM3m2NPNR L42CQWzroAZI9Vlv2U1ZrW9HnYIMo0SgujnFsZiZmR1WPlWxB+ZYA/yvcZffcuCcMd1f Bts1hvyHTLXVOSunPM1/ecvA9lZDElarQlPYJv+Q5+0MWL1bnAbhbL+JSCSazLOJJz7L P6iTDqshb72vgZ0tuW5zVSk9DvGb49oXHPAGKehlBIc4gOL8OxsH5Gv/NRMynxzaUhGY ETkQ== X-Gm-Message-State: APjAAAWgZDyl070ngCfBuq2kb3tGMN9qSM1YFmbmCRsN4Cmkpwle4f87 8cJZd7lvwhXHzS6na6xunFZoO03kck0= X-Received: by 2002:a17:902:2bab:: with SMTP id l40mr5876361plb.273.1553058583841; Tue, 19 Mar 2019 22:09:43 -0700 (PDT) Received: from localhost ([122.177.144.121]) by smtp.gmail.com with ESMTPSA id p86sm1298564pfa.104.2019.03.19.22.09.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Mar 2019 22:09:42 -0700 (PDT) From: Bhupesh Sharma To: linux-kernel@vger.kernel.org Cc: bhsharma@redhat.com, bhupesh.linux@gmail.com, Mark Rutland , James Morse , Will Deacon , Boris Petkov , Ingo Molnar , Thomas Gleixner , Michael Ellerman , Paul Mackerras , Benjamin Herrenschmidt , Dave Anderson , Kazuhito Hagio , x86@kernel.org, linuxppc-dev@lists.ozlabs.org, linux-arm-kernel@lists.infradead.org, kexec@lists.infradead.org Subject: [PATCH v3 0/3] Append new variables to vmcoreinfo (PTRS_PER_PGD for arm64 and MAX_PHYSMEM_BITS for all archs) Date: Wed, 20 Mar 2019 10:39:31 +0530 Message-Id: <1553058574-18606-1-git-send-email-bhsharma@redhat.com> X-Mailer: git-send-email 2.7.4 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Changes since v2: ---------------- - v2 can be seen here: http://lists.infradead.org/pipermail/kexec/2019-March/022531.html - Protected 'MAX_PHYSMEM_BITS' vmcoreinfo variable under CONFIG_SPARSEMEM ifdef sections, as suggested by Kazu. - Updated vmcoreinfo documentation to add description about 'MAX_PHYSMEM_BITS' variable (via [PATCH 3/3]). Changes since v1: ---------------- - v1 was sent out as a single patch which can be seen here: http://lists.infradead.org/pipermail/kexec/2019-February/022411.html - v2 breaks the single patch into two independent patches: [PATCH 1/2] appends 'PTRS_PER_PGD' to vmcoreinfo for arm64 arch, whereas [PATCH 2/2] appends 'MAX_PHYSMEM_BITS' to vmcoreinfo in core kernel code (all archs) This patchset primarily fixes the regression reported in user-space utilities like 'makedumpfile' and 'crash-utility' on arm64 architecture with the availability of 52-bit address space feature in underlying kernel. These regressions have been reported both on CPUs which don't support ARMv8.2 extensions (i.e. LVA, LPA) and are running newer kernels and also on prototype platforms (like ARMv8 FVP simulator model) which support ARMv8.2 extensions and are running newer kernels. The reason for these regressions is that right now user-space tools have no direct access to these values (since these are not exported from the kernel) and hence need to rely on a best-guess method of determining value of 'PTRS_PER_PGD' and 'MAX_PHYSMEM_BITS' supported by underlying kernel. Exporting these values via vmcoreinfo will help user-land in such cases. In addition, as per suggestion from makedumpfile maintainer (Kazu), it makes more sense to append 'MAX_PHYSMEM_BITS' to vmcoreinfo in the core code itself rather than in arm64 arch-specific code, so that the user-space code for other archs can also benefit from this addition to the vmcoreinfo and use it as a standard way of determining 'SECTIONS_SHIFT' value in user-land. Cc: Mark Rutland Cc: James Morse Cc: Will Deacon Cc: Boris Petkov Cc: Ingo Molnar Cc: Thomas Gleixner Cc: Michael Ellerman Cc: Paul Mackerras Cc: Benjamin Herrenschmidt Cc: Dave Anderson Cc: Kazuhito Hagio Cc: x86@kernel.org Cc: linuxppc-dev@lists.ozlabs.org Cc: linux-arm-kernel@lists.infradead.org Cc: linux-kernel@vger.kernel.org Cc: kexec@lists.infradead.org Bhupesh Sharma (3): arm64, vmcoreinfo : Append 'PTRS_PER_PGD' to vmcoreinfo crash_core, vmcoreinfo: Append 'MAX_PHYSMEM_BITS' to vmcoreinfo Documentation/vmcoreinfo: Add documentation for 'MAX_PHYSMEM_BITS' Documentation/kdump/vmcoreinfo.txt | 5 +++++ arch/arm64/kernel/crash_core.c | 1 + kernel/crash_core.c | 1 + 3 files changed, 7 insertions(+) -- 2.7.4