On 23.10.2023 11:20, Zhenhua Huang wrote:
Qualcomm memory dump driver is to cooperate with firmware, providing theFirmware == The hypervisor? The TZ? Some uncore chip?
hints(id and size) of storing useful debugging information into pre-allocatedExposing all of the user's data.. Is this enabled by default?
memory. Firmware then does the real data capture. The debugging information
includes cache contents, internal memory, registers.
Is that only something that works on engineering / prototype devices?
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.Is PCAT open-source, or at least freely available?
Is it the same bootconfig that Google invented? Wasn't that just key=val?
Dump id and size are provided by bootconfig. The expected format of a
bootconfig file is as follows:-
memory_dump_config {That's sorta ancient, especially since you're likely looking to get
<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.
this merged in 6.8.. -next would probably be a better target.
Konrad