[lkml]   [2013]   [Nov]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] x86, efi: change name of efi_no_storage_paranoia parameter to efi_storage_paranoia
Date writes:

> Hi Matt,
> Sorry for late the reply.
> (2013/11/11 19:54), Matt Fleming wrote:
>> On Mon, 11 Nov, at 05:52:59PM, Yasuaki Ishimatsu wrote:
>>> Hi Matt,
>>> I uses FUJITSU's x86 box.
>>> This does not become bricked even if I use all efi variable storage.
>>> Thus I want a way to not need to specify efi_no_storage_paranoia
>>> parameter.
>> The efi_no_storage_paranoia parameter was introduced because some
>> machines do not initiate garbage collection of the NVRAM until you
>> allocate all space - basically it's a switch to turn off the "save 5KB
>> of stoarge at all times" workaround that is needed to avoid bricking
>> some machines.
>> The intention of the switch is not to allow you to fill your NVRAM just
>> because you can. If that is something you want to do then I think it's
>> fair to require you to explicitly turn on efi_no_storage_paranoia. But
>> I'm assuming here that you are doing something like writing lots and
>> lots of pstore entries and just want to write as many as your variable
>> storage will allow? Or are you doing something more fundamental like
>> creating BootXXXX entries?
>> What are you doing to run into the 5KB reserve? How much NVRAM does your
>> machine come with?
> I just add boot entry to NVRAM by efibootmgr command. But when Linux boots up,
> the remaining NVRAM is less than 5Kbyte. So I cannnot add new entry.
Howdy Yasuaki,
If the remaining NVRAM is less than 5Kb, your writing will trigger a
NVRAM storage reclamation. However you still failed creating entry. So
I'm just curious what itmes occupy lots of nvram storage space.

> Thanks,
> Yasuaki Ishimatsu


 \ /
  Last update: 2013-11-19 04:41    [W:0.063 / U:0.100 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site