From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751676Ab3KSDRB (ORCPT ); Mon, 18 Nov 2013 22:17:01 -0500 Received: from mx1.redhat.com ([209.132.183.28]:64648 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751350Ab3KSDQ5 (ORCPT ); Mon, 18 Nov 2013 22:16:57 -0500 References: <527C93B5.7010407@jp.fujitsu.com> <527C9B5C.6040509@nod.at> <527CB013.30200@jp.fujitsu.com> <527CB0F4.8080606@nod.at> <527CBC05.6080505@jp.fujitsu.com> <527CBD01.1000908@nod.at> <527CBDD3.2020609@jp.fujitsu.com> <20131108143421.GB22636@console-pimps.org> <52809AEB.9080100@jp.fujitsu.com> <20131111105424.GD22636@console-pimps.org> <528AD50D.6060503@jp.fujitsu.com> User-agent: mu4e 0.9.9.6pre2; emacs 24.3.1 From: Madper Xie To: Yasuaki Ishimatsu Cc: Matt Fleming , Richard Weinberger , 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 In-reply-to: <528AD50D.6060503@jp.fujitsu.com> Date: Tue, 19 Nov 2013 11:16:32 +0800 Message-ID: <87siutqdwv.fsf@redhat.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. > Thanks, > Yasuaki Ishimatsu -- Best, Madper