linux-kernel - [PATCH v1 0/5] soc/arm64: qcom: add initial version of memory dump

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <1698052857-6918-1-git-send-email-quic_zhenhuah@quicinc.com>
Date:   Mon, 23 Oct 2023 17:20:52 +0800
From:   Zhenhua Huang <quic_zhenhuah@...cinc.com>
To:     <agross@...nel.org>, <andersson@...nel.org>,
        <konrad.dybcio@...aro.org>, <robh+dt@...nel.org>,
        <krzysztof.kozlowski+dt@...aro.org>, <conor+dt@...nel.org>
CC:     <linux-arm-msm@...r.kernel.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <kernel@...cinc.com>,
        <quic_tingweiz@...cinc.com>,
        Zhenhua Huang <quic_zhenhuah@...cinc.com>
Subject: [PATCH v1 0/5] soc/arm64: qcom: add initial version of memory dump

Qualcomm memory dump driver is to cooperate with firmware, providing the
hints(id and size) of storing useful debugging information into pre-allocated
memory. Firmware then does the real data capture. The debugging information
includes cache contents, internal memory, registers. 

The driver dynamically reserves memory and provides the hints(dump id and size)
following specified protocols with firmware. After crash and warm reboot,
firmware scans these information and stores contents into reserved memory
accordingly. Firmware then enters into full dump mode which dumps whole DDR
to host through USB.

User then get full dump using PCAT and can parse out these informations.

Dump id and size are provided by bootconfig. The expected format of a
bootconfig file is as follows:-
memory_dump_config {
	<node name> {
		id = <id of HW component>
		size = <dump size of HW component>
	}
}

for example:
memory_dump_config {
        c0_context_dump {
		id = 0
		size = 0x800
        }
}

Test based on 6.6-rc1.

Zhenhua Huang (5):
  dt-bindings: soc: qcom: Add memory_dump driver bindings
  dt-bindings: sram: qcom,imem: document sm8250
  soc: qcom: memory_dump: Add memory dump driver
  arm64: defconfig: enable Qcom Memory Dump driver
  arm64: dts: qcom: sm8250: Add memory dump node

 .../bindings/soc/qcom/qcom,mem-dump.yaml           |  42 ++
 .../devicetree/bindings/sram/qcom,imem.yaml        |  45 ++
 MAINTAINERS                                        |   7 +
 arch/arm64/boot/dts/qcom/sm8250.dtsi               |  31 ++
 arch/arm64/configs/defconfig                       |   1 +
 drivers/soc/qcom/Kconfig                           |  11 +
 drivers/soc/qcom/Makefile                          |   1 +
 drivers/soc/qcom/memory_dump.c                     | 540 +++++++++++++++++++++
 8 files changed, 678 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,mem-dump.yaml
 create mode 100644 drivers/soc/qcom/memory_dump.c

-- 
2.7.4