Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp8519585ybc; Fri, 29 Nov 2019 12:01:10 -0800 (PST) X-Google-Smtp-Source: APXvYqzXBbQ3fRN6tzCcSfcCN7RG/MZQ8bQNeEl+9BIPK2lVRi8jiv5r1j4wDyz+5TsXVT/EkKzj X-Received: by 2002:a17:906:240c:: with SMTP id z12mr64267946eja.35.1575057669834; Fri, 29 Nov 2019 12:01:09 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575057669; cv=none; d=google.com; s=arc-20160816; b=Mhw6vnQQCliu8EvStIdBteLPZxjh2XCG6VW3kulp9KUhv3vImhTLjfZeUO7Fpx2/Eh iSiMSCKbwQ6LxdSBVgA4doqHlB3aAEr+We/sitASfAEEvY1w8XmZfB5i9p0kh3zDMqmj LAftdcTwU8l7Tjk2+T2/FpypZs9tEaASjgkGWph/gvDPNcizv0XYQuCQijrgjiLFXBq1 aBoNmI/R+K6Q38/NmIqWmhMoI1NAQNXLwgKPlxrWdORLFL3h+9BzlfT4cWOQW3DbWsHF 1w6s5L9KB7OMcuWGT/L2uJhDu/QtQQYv/ugSFJpfBeHQ+pziuFzkFUEcnePeYT6AZWyv L2vg== 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:message-id:date :subject:cc:to:from:dkim-signature; bh=PGjdyVBK0NO+k94paV7/u4ZDFA/aVBH6mgmJUwldOho=; b=cImKSfJ0IKEYaOHo0FTk1fBJRfjEuef0sqmyZOSCwLygEZ6nmE4kb4sbA09BljJV72 WkiyYwGdWwCAiEWVvwZecKHzYiRVEwRjbvUxi9IJ01Teptg+wKZ0qnWLmHLER18hwqLe ADIedHn5FLCSWHh0qUEQg0icSTRg3/74HZnMyH8596MX3TaIlX561lqq8crFjHyazbSw +g99P/sSHthXVK2B6mWMHMBXzd1tU5KUhieH0zDujWGWh0Xc/tCii9HH78TiGKnS9GuZ Sw2hDvPcDTTDEpcas8ODwHxP+FWeUZ0oDacQ11Wrsg3FuIoyC578xE1b3l6gM2zr6lgf CeBQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=EULtTY0r; 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=pass (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 n16si7181310eda.345.2019.11.29.12.00.38; Fri, 29 Nov 2019 12:01:09 -0800 (PST) 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; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=EULtTY0r; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727090AbfK2T7g (ORCPT + 99 others); Fri, 29 Nov 2019 14:59:36 -0500 Received: from us-smtp-delivery-1.mimecast.com ([205.139.110.120]:42723 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726926AbfK2T7f (ORCPT ); Fri, 29 Nov 2019 14:59:35 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1575057574; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=PGjdyVBK0NO+k94paV7/u4ZDFA/aVBH6mgmJUwldOho=; b=EULtTY0rCCJyppwfezZNt4URfB2u1K8fWfC1SChVZvywhTvso6ninA+w2j0iVhaJ4CwWtU hok65mORdwUzwPyDFZ7JxV5bLlQM4+RErb4Mg1CFpub9i/hP0p1C43pmWs2eXYKmCA54dk YhjFbg6EAN3u9C05PfvT0SwtT3cqo2c= Received: from mail-pg1-f199.google.com (mail-pg1-f199.google.com [209.85.215.199]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-148-SdUH3T6NM0qBGycBwIWKsw-1; Fri, 29 Nov 2019 14:59:32 -0500 Received: by mail-pg1-f199.google.com with SMTP id k10so17082926pgm.7 for ; Fri, 29 Nov 2019 11:59:32 -0800 (PST) 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=XYOfM9R2XBKHHSS98VDt4f7vGAptvryNwXrf29d+FoM=; b=J2ug9VPg/Gp31s6xLYqAcnUm3vfzUvinL67QGry9S9AvniKt90T2RFE3NYgplxNS10 EXbwVTdw13sntYtSXK0IzjhTLfk4BSPLep1dPNOfqMnCVm58Jc+tI/c2JPVJa7u1LgRF LjwvlyB8f/S0pIvGy/5EF+vjsqZOFNyYoLJxw6/KQaJ3s2e168MvqxvJbmp6KWZHulbu hg43ESQfinV2bSMqLxW7TPSRyWvLdKj25j48Ftx4B/kFi7CTQcUjz5sfJ3W+UDkeo0dc xD1sWMQt+q0bqUZR0ncSJxW92YgY9BEGRGLPGLg7BcOvVhxhz1nH640r9K2/L71J32wk KJOg== X-Gm-Message-State: APjAAAVR+ibFJKhgAgXmOUzlLelDdjCLzaTps6TiyX9UsHGAWA3RLLD/ sA0mUSfzH+BYui62uw34ckkybON74j6RlQD3VaSLmtopyibJCfySBb2ZiYJoVfL9mc+P6mwioDU GDstSEukTICmhPMWFOtN3j2Va X-Received: by 2002:a17:902:8306:: with SMTP id bd6mr16507170plb.44.1575057571079; Fri, 29 Nov 2019 11:59:31 -0800 (PST) X-Received: by 2002:a17:902:8306:: with SMTP id bd6mr16507151plb.44.1575057570720; Fri, 29 Nov 2019 11:59:30 -0800 (PST) Received: from localhost ([122.177.85.74]) by smtp.gmail.com with ESMTPSA id s7sm10138820pfe.22.2019.11.29.11.59.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 29 Nov 2019 11:59:29 -0800 (PST) From: Bhupesh Sharma To: linux-kernel@vger.kernel.org Cc: bhsharma@redhat.com, bhupesh.linux@gmail.com, x86@kernel.org, linuxppc-dev@lists.ozlabs.org, linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org, kexec@lists.infradead.org, Boris Petkov , Ingo Molnar , Thomas Gleixner , Jonathan Corbet , James Morse , Mark Rutland , Will Deacon , Steve Capper , Catalin Marinas , Ard Biesheuvel , Michael Ellerman , Paul Mackerras , Benjamin Herrenschmidt , Dave Anderson , Kazuhito Hagio Subject: [RESEND PATCH v5 0/5] Append new variables to vmcoreinfo (TCR_EL1.T1SZ for arm64 and MAX_PHYSMEM_BITS for all archs) Date: Sat, 30 Nov 2019 01:29:14 +0530 Message-Id: <1575057559-25496-1-git-send-email-bhsharma@redhat.com> X-Mailer: git-send-email 2.7.4 X-MC-Unique: SdUH3T6NM0qBGycBwIWKsw-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org - Resending the v5 version as Will Deacon reported that the patchset was split into two seperate threads while sending out. It was an issue with my 'msmtp' settings which seems to be now fixed. Please ignore all previous v5 versions. Changes since v4: ---------------- - v4 can be seen here: http://lists.infradead.org/pipermail/kexec/2019-November/023961.html - Addressed comments from Dave and added patches for documenting new variables appended to vmcoreinfo documentation. - Added testing report shared by Akashi for PATCH 2/5. Changes since v3: ---------------- - v3 can be seen here: http://lists.infradead.org/pipermail/kexec/2019-March/022590.html - Addressed comments from James and exported TCR_EL1.T1SZ in vmcoreinfo instead of PTRS_PER_PGD. - Added a new patch (via [PATCH 3/3]), which fixes a simple typo in 'Documentation/arm64/memory.rst' 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 'vabits_actual' 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: Boris Petkov Cc: Ingo Molnar Cc: Thomas Gleixner Cc: Jonathan Corbet Cc: James Morse Cc: Mark Rutland Cc: Will Deacon Cc: Steve Capper Cc: Catalin Marinas Cc: Ard Biesheuvel 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: linux-doc@vger.kernel.org Cc: kexec@lists.infradead.org Bhupesh Sharma (5): crash_core, vmcoreinfo: Append 'MAX_PHYSMEM_BITS' to vmcoreinfo arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo Documentation/arm64: Fix a simple typo in memory.rst Documentation/vmcoreinfo: Add documentation for 'MAX_PHYSMEM_BITS' Documentation/vmcoreinfo: Add documentation for 'TCR_EL1.T1SZ' Documentation/admin-guide/kdump/vmcoreinfo.rst | 11 +++++++++++ Documentation/arm64/memory.rst | 2 +- arch/arm64/include/asm/pgtable-hwdef.h | 1 + arch/arm64/kernel/crash_core.c | 9 +++++++++ kernel/crash_core.c | 1 + 5 files changed, 23 insertions(+), 1 deletion(-) --=20 2.7.4