From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: Madper Xie <cxie@redhat.com>
Cc: Matt Fleming <matt@console-pimps.org>,
Richard Weinberger <richard@nod.at>, <linux-efi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <matt.fleming@intel.com>,
<matthew.garrett@nebula.com>, <jlee@suse.com>
Subject: Re: [PATCH] x86, efi: change name of efi_no_storage_paranoia parameter to efi_storage_paranoia
Date: Wed, 20 Nov 2013 15:26:51 +0900 [thread overview]
Message-ID: <528C562B.3070008@jp.fujitsu.com> (raw)
In-Reply-To: <87siutqdwv.fsf@redhat.com>
(2013/11/19 12:16), Madper Xie wrote:
>
> isimatu.yasuaki@jp.fujitsu.com 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.
Even if we got EFI_OUT_OF_RESOURCES while running Linux, gc does not run.
Trigger of gc is when EFI_OUT_OF_RESOURCES occurs on pre OS environment with
UEFI. So on my system, if EFI_OUT_OF_RESOURCES occurs by the 5Kbyte threshold,
we cannot use nvram storage until EFI_OUT_OF_RESOURCES occurs on pre OS
environment with UEFI.
Thanks,
Yasuaki Ishimatsu
>
>> Thanks,
>> Yasuaki Ishimatsu
>
> --
> Best,
> Madper
>
next prev parent reply other threads:[~2013-11-20 6:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 7:33 [PATCH] x86, efi: change name of efi_no_storage_paranoia parameter to efi_storage_paranoia Yasuaki Ishimatsu
2013-11-08 8:05 ` Richard Weinberger
2013-11-08 8:46 ` Madper Xie
2013-11-08 9:34 ` Yasuaki Ishimatsu
2013-11-08 9:37 ` Richard Weinberger
2013-11-08 10:25 ` Yasuaki Ishimatsu
2013-11-08 10:29 ` Richard Weinberger
2013-11-08 10:32 ` Yasuaki Ishimatsu
2013-11-08 14:34 ` Matt Fleming
2013-11-11 8:52 ` Yasuaki Ishimatsu
2013-11-11 9:47 ` Madper Xie
2013-11-11 10:54 ` Matt Fleming
2013-11-19 3:03 ` Yasuaki Ishimatsu
2013-11-19 3:16 ` Madper Xie
2013-11-20 6:26 ` Yasuaki Ishimatsu [this message]
2013-11-20 8:08 ` joeyli
2013-11-21 9:13 ` Yasuaki Ishimatsu
2013-11-21 9:53 ` joeyli
2013-11-21 10:27 ` joeyli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=528C562B.3070008@jp.fujitsu.com \
--to=isimatu.yasuaki@jp.fujitsu.com \
--cc=cxie@redhat.com \
--cc=jlee@suse.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matt@console-pimps.org \
--cc=matthew.garrett@nebula.com \
--cc=richard@nod.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox