Hi, Just for information, We have recently presented at LPC2023 Abstract and PDF here: https://lpc.events/event/17/contributions/1468/ Video: 07:09:00 hrs at https://www.youtube.com/watch?v=68EBBgEltXA This series should be applied on top of below series of some SCM patches sent here. https://lore.kernel.org/lkml/1698945247-16033-1-git-send-email-quic_mojha@xxxxxxxxxxx/ Patch 1-2 enable support to enable multiple download mode Patch 3 deals in detail documentation on minidump. Patch 4-6 refactors minidump existing layout and separate it from remoteproc files. Patch 8 is the Qualcomm apss minidump driver. Patch 10-12 Enable support to reserve dynamic ramoops and the support to register ramoops region with minidump. Changes in v6: - Accumalated the feedback received on v5 and rebase v5 versions in v6. - Removed the exported function as there is no current users of them. - Applied [Pavan.K] suggestion on caller/callee placement of dynamic ramoops reserve memory. - Addressed [krzysztof] comment on sizeof() and to have qcom_apss_md_table_exit(). - Addressed [Bagas.S] comment on minidump doc. - Tried to implement [Kees] suggestion in slight different way with callback registration with ramoops instead of pstore core. Change in rebase v5: https://lore.kernel.org/lkml/1694429639-21484-1-git-send-email-quic_mojha@xxxxxxxxxxx/ - Rebased it on latest tag available on linux-next - Added missed Poovendhan sign-off on 15/17 and tested-by tag from Kathiravan. Thanks to him for testing and reminding me of missing sign-off. Changes in v5: https://lore.kernel.org/lkml/1694290578-17733-1-git-send-email-quic_mojha@xxxxxxxxxxx/ - On suggestion from Pavan.k, to have single function call for minidump collection from remoteproc driver, separated the logic to have separate minidump file called qcom_rproc_minidump.c and also renamed the function from qcom_minidump() to qcom_rproc_minidump(); however, dropped his suggestion about rework on lazy deletion during region unregister in this series, will pursue it in next series. - To simplify the minidump driver, removed the complication for frontend and different backend from Greg suggestion, will pursue this once main driver gets mainlined. - Move the dynamic ramoops region allocation from Device tree approach to command line approch with the introduction command line parsing and memblock reservation during early boot up; Not added documentation about it yet, will add if it gets positive response. - Exporting linux banner from kernel to make minidump build also as module, however, minidump is a debug module and should be kernel built to get most debug information from kernel. - Tried to address comments given on dload patch series. Changes in v4: https://lore.kernel.org/lkml/1687955688-20809-1-git-send-email-quic_mojha@xxxxxxxxxxx/ - Redesigned the driver and divided the driver into front end and backend (smem) so that any new backend can be attached easily to avoid code duplication. - Patch reordering as per the driver and subsystem to easier review of the code. - Removed minidump specific code from remoteproc to minidump smem based driver. - Enabled the all the driver as modules. - Address comments made on documentation and yaml and Device tree file [Krzysztof/Konrad] - Address comments made qcom_pstore_minidump driver and given its Device tree same set of properties as ramoops. [Luca/Kees] - Added patch for MAINTAINER file. - Include defconfig change as one patch as per [Krzysztof] suggestion. - Tried to remove the redundant file scope variables from the module as per [Krzysztof] suggestion. - Addressed comments made on dload mode patch v6 version https://lore.kernel.org/lkml/1680076012-10785-1-git-send-email-quic_mojha@xxxxxxxxxxx/ Changes in v3: https://lore.kernel.org/lkml/1683133352-10046-1-git-send-email-quic_mojha@xxxxxxxxxxx/ - Addressed most of the comments by Srini on v2 and refactored the minidump driver. - Added platform device support - Unregister region support. - Added update region for clients. - Added pending region support. - Modified the documentation guide accordingly. - Added qcom_pstore_ramdump client driver which happen to add ramoops platform device and also registers ramoops region with minidump. - Added download mode patch series with this minidump series. https://lore.kernel.org/lkml/1680076012-10785-1-git-send-email-quic_mojha@xxxxxxxxxxx/ Changes in v2: https://lore.kernel.org/lkml/1679491817-2498-1-git-send-email-quic_mojha@xxxxxxxxxxx/ - Addressed review comment made by [quic_tsoni/bmasney] to add documentation. - Addressed comments made by [srinivas.kandagatla] - Dropped pstore 6/6 from the last series, till i get conclusion to get pstore region in minidump. - Fixed issue reported by kernel test robot. Changes in v1: https://lore.kernel.org/lkml/1676978713-7394-1-git-send-email-quic_mojha@xxxxxxxxxxx/ Minidump is a best effort mechanism to collect useful and predefined data for first level of debugging on end user devices running on Qualcomm SoCs. It is built on the premise that System on Chip (SoC) or subsystem part of SoC crashes, due to a range of hardware and software bugs. Qualcomm devices in engineering mode provides a mechanism for generating full system ramdumps for post mortem debugging. But in some cases it's however not feasible to capture the entire content of RAM. The minidump mechanism provides the means for selecting which snippets should be included in the ramdump. The core of SMEM based minidump feature is part of Qualcomm's boot firmware code. It initializes shared memory (SMEM), which is a part of DDR and allocates a small section of SMEM to minidump table i.e also called global table of content (G-ToC). Each subsystem (APSS, ADSP, ...) has their own table of segments to be included in the minidump and all get their reference from G-ToC. Each segment/region has some details like name, physical address and it's size etc. and it could be anywhere scattered in the DDR. Existing upstream Qualcomm remoteproc driver[1] already supports SMEM based minidump feature for remoteproc instances like ADSP, MODEM, ... where predefined selective segments of subsystem region can be dumped as part of coredump collection which generates smaller size artifacts compared to complete coredump of subsystem on crash. [1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/remoteproc/qcom_common.c#n142 In addition to managing and querying the APSS minidump description, the Linux driver maintains a ELF header in a segment. This segment gets updated with section/program header whenever a new entry gets registered. Testing of these patches has been done on sm8450 target after enabling config like CONFIG_PSTORE_RAM/CONFIG_PSTORE_CONSOLE and once the device boots up. echo mini > /sys/module/qcom_scm/parameters/download_mode Try crashing it via devmem2 0xf11c000(this is known to create xpu violation and and put the device in download mode) on command prompt. Default storage type is set to via USB, so minidump would be downloaded with the help of x86_64 machine (running PCAT tool) attached to Qualcomm device which has backed minidump boot firmware support. This will make the device go to download mode and collect the minidump on to the attached x86 machine running the Qualcomm PCAT tool(This comes as part Qualcomm package manager kit). After that we will see a bunch of predefined registered region as binary blobs files starts with md_* downloaded on the x86 machine on given location in PCAT tool from the target device, more about this can be found in qualcomm minidump guide patch. Mukesh Ojha (12): firmware: qcom_scm: Refactor code to support multiple dload mode firmware/qcom: qcom_scm: Add multiple download mode support docs: qcom: Add qualcomm minidump guide soc: qcom: Add qcom_rproc_minidump module remoteproc: qcom_q6v5_pas: Use qcom_rproc_minidump() remoteproc: qcom: Remove minidump related data from qcom_common.c init: export linux_banner data variable soc: qcom: Add Qualcomm APSS minidump kernel driver MAINTAINERS: Add entry for minidump related files pstore/ram: Add dynamic ramoops region support through commandline pstore/ram: Add ramoops ready notifier support soc: qcom: register ramoops region with APSS minidump Documentation/admin-guide/index.rst | 1 + Documentation/admin-guide/qcom_minidump.rst | 272 +++++++++++ Documentation/admin-guide/ramoops.rst | 7 + MAINTAINERS | 10 + drivers/firmware/qcom/Kconfig | 11 - drivers/firmware/qcom/qcom_scm.c | 62 ++- drivers/remoteproc/Kconfig | 1 + drivers/remoteproc/qcom_common.c | 160 ------- drivers/remoteproc/qcom_q6v5_pas.c | 3 +- drivers/soc/qcom/Kconfig | 23 + drivers/soc/qcom/Makefile | 2 + drivers/soc/qcom/qcom_minidump.c | 668 ++++++++++++++++++++++++++++ drivers/soc/qcom/qcom_minidump_internal.h | 74 +++ drivers/soc/qcom/qcom_rproc_minidump.c | 111 +++++ drivers/soc/qcom/smem.c | 20 + fs/pstore/Kconfig | 15 + fs/pstore/ram.c | 139 +++++- include/linux/init.h | 3 + include/linux/pstore_ram.h | 11 + include/linux/soc/qcom/smem.h | 2 + include/soc/qcom/qcom_minidump.h | 41 ++ init/main.c | 2 + init/version-timestamp.c | 3 + 23 files changed, 1456 insertions(+), 185 deletions(-) create mode 100644 Documentation/admin-guide/qcom_minidump.rst create mode 100644 drivers/soc/qcom/qcom_minidump.c create mode 100644 drivers/soc/qcom/qcom_minidump_internal.h create mode 100644 drivers/soc/qcom/qcom_rproc_minidump.c create mode 100644 include/soc/qcom/qcom_minidump.h -- 2.7.4
