On 28 May 2014 20:04, Vivek Goyal <vgoyal@xxxxxxxxxx> wrote: > On Wed, May 28, 2014 at 10:51:04AM -0500, Alex Thorlton wrote: > > [..] >> A side note, though: We're going to have to figure out some way to >> determine whether or not to apply the old_map quirk on during boot >> anyway, so if it's easiest for you to just determine how the original >> kernel was booted and key off of that, then I wouldn't worry about >> finding a different method to get the firmware version in userspace, >> unless there are other reasons for you to do it that way. > > Agreed. Let kernel and firmware figure it out when to apply quirk and > user space should not worry about firmware version. > > I liked the other approach better where user space just needs to know > if 1:1 mapping are in effect or not and take decision based on that. The problem with going down this route is that if we ever change the way we map the EFI regions in the kernel corresponding changes will be required for kexec-tools. That's not ideal. Kexec-tools should not be interpreting /sys/firmware/efi/runtime-map/ any further than building a memory map, i.e. it has to understand how to build a memory region descriptor but it shouldn't care what *values* are in them. -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
