)]}'
{
  "commit": "20b53c6f7041e7d09d77fe6bab84e755c739d6f1",
  "tree": "8b47d9ce62ea359bf4fc3cfe03567970cfbfa317",
  "parents": [
    "dc59e4fea9d83f03bad6bddf3fa2e52491777482",
    "a037fe3c58ed489ca8ad8531bd7e16b90a84badc"
  ],
  "author": {
    "name": "Mike Rapoport (Microsoft)",
    "email": "rppt@kernel.org",
    "time": "Tue Jun 30 18:49:07 2026 +0300"
  },
  "committer": {
    "name": "Mike Rapoport (Microsoft)",
    "email": "rppt@kernel.org",
    "time": "Tue Jun 30 18:49:07 2026 +0300"
  },
  "message": "Merge patch series \"arm64/riscv: Add support for crashkernel CMA reservation\"\n\nJinjie Ruan \u003cruanjinjie@huawei.com\u003e says:\n\nThe crash memory allocation, and the exclusion of crashk_res,\ncrashk_low_res and crashk_cma memory are almost identical across\ndifferent architectures.\n\nHandle them in crash core in a generic way, to eliminate a lot of\ncode duplication.\n\nAnd add support for crashkernel CMA reservation for arm64 and riscv.\n\nBasic second kernel boot test were performed on QEMU platforms for x86,\nARM64 and RISC-V architectures with the following parameters:\n\n        \"cma\u003d256M crashkernel\u003d4G crashkernel\u003d64M,cma\"\n\nFor first kernel, there will be such log:\n\n        # dmesg | grep crash\n        [    0.000000] crashkernel low memory reserved: 0xe8000000 - 0xf0000000 (128 MB)\n        [    0.000000] crashkernel reserved: 0x000000023e600000 - 0x000000033e600000 (4096 MB)\n        [    0.000000] crashkernel CMA reserved: 64 MB in 1 ranges\n\n        # dmesg | grep cma\n        [    0.000000] cma: Reserved 256 MiB at 0x00000000f0000000\n        [    0.000000] cma: Reserved 64 MiB at 0x0000000100000000\n\nFor second kernel, there will be such log:\n\n        [    0.000000] OF: fdt: Looking for usable-memory-range property...\n        [    0.000000] OF: fdt: cap_mem_regions[0]: base\u003d0x000000023e600000, size\u003d0x0000000100000000\n        [    0.000000] OF: fdt: cap_mem_regions[1]: base\u003d0x00000000e8000000, size\u003d0x0000000008000000\n        [    0.000000] OF: fdt: cap_mem_regions[2]: base\u003d0x0000000100000000, size\u003d0x0000000004000000\n\n* patches from https://patch.msgid.link/20260629094746.191843-1-ruanjinjie@huawei.com\n  riscv: kexec_file: Fix crashk_low_res not exclude bug\n  crash: Add crash_prepare_headers() to exclude crash kernel memory\n  arm64: kexec_file: Use crash_prepare_headers() helper to simplify code\n  x86/crash: Use crash_prepare_headers() helper to simplify code\n  riscv: kexec_file: Use crash_prepare_headers() helper to simplify code\n  LoongArch: kexec_file: Use crash_prepare_headers() helper to simplify\n    code\n  powerpc/kexec_file: Use crash_exclude_core_ranges() helper\n  arm64: kexec_file: Add support for crashkernel CMA reservation\n  riscv: kexec_file: Add support for crashkernel CMA reservation\n  powerpc/crash: sort crash memory ranges before preparing elfcorehdr\n\nLink: https://patch.msgid.link/20260629094746.191843-1-ruanjinjie@huawei.com\nSigned-off-by: Mike Rapoport (Microsoft) \u003crppt@kernel.org\u003e\n",
  "tree_diff": []
}