{"ref":"refs/heads/master","commits":[{"author":{"email":"db4757c56f54651f568cc7cda79cd93c781b1605@linux.vnet.ibm.com","name":"Michael Holzheu"},"sha":"746723f266fff28223899e9b366f14d4854b08ff","message":"kexec-tools: s390: Do not create ELF header by default\n\nFor s390 we have two modes for kdump:\n\nFor the first mode, as on all other architectures, the kexec tool creates\nthe ELF header and the 2nd kernel processes it for /proc/vmcore setup.\n\nThis mode has the disadvantage that for memory and CPU hotplug the kdump\nkernel has to be reloaded by the kexec tool. For s390 this is a real problem\nbecause we have a cpuplugd daemon that sets CPUs online and offline\naccording to the current workload. So CPU online/offline events occur very\noften.\n\nFor the second mode on s390, the ELF header is created by the kdump kernel.\nThis is done automatically when the kernel is booted in kdump mode\nand no \"elfcorehdr\" kernel parameter is specified. On s390 the kdump kernel\ncan get all necessary information to build the ELF header. We can get\nthe memory map, all CPU registers, and vmcoreinfo\n\nWith this patch a compile switch WITH_ELF_HEADER is introduced. When the\nmacro is defined, kexec will create the ELF header and add the \"elfcorehdr\"\nkernel parameter. If it is not specified (default), no header is created.\n\nFor s390 we want to have the 2nd mode as default because it has only\nadvantages for us.\n\nSigned-off-by: Michael Holzheu <holzheu@linux.vnet.ibm.com>\nSigned-off-by: Simon Horman <horms@verge.net.au>","url":"https://api.github.com/repos/horms/kexec-tools/commits/746723f266fff28223899e9b366f14d4854b08ff"}],"head":"746723f266fff28223899e9b366f14d4854b08ff","push_id":53441888,"size":1}