Hi Jerry, On Tue, Nov 12, 2013 at 7:55 PM, <jerry.hoem...@hp.com> wrote: > My change does not address platforms that have misbehaving firmware. > It just allows platforms that don't have this issue to avoid issues > that the call to efi_reserve_boot_services presents.
The problem I have with your patch is that it (1) relies on users to pass a kernel option and (2) leaves machines with "faulty firmware" out in the cold. So I'm wondering if we can fix reserve_crashkernel() to deal with reality that there indeed are broken firmware out there? If someone is able to come up with a convincing argument why crashkernel cannot be fixed on such machines, we'd need to start whitelisting known good firmwares, no? Pekka -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/