RE: [RFC][Patch]efi_pstore:Introduce an efi_pstore_overwrite parameter to avoid missing messages in NVRAM

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Should it be in pstore layer?
>  - introducing a new global variable storing a previous trigger.
>  - deciding if we can continue by checking a value of previous trigger at the beginning of pstore_dump().

I think not - the limitation is EFI (ERST can handle several errors, I think that the ramoops
patches are working with the assumption that enough storage is available too).

The question is how easy is it for EFI to determine the "type" of the saved
error (which may be from the previous booted kernel - so no use using a
global variable ... the information needs to be in persistent store).

-Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux