From: Matthew Garrett <matthew.garrett@nebula.com>
To: "isimatu.yasuaki@jp.fujitsu.com" <isimatu.yasuaki@jp.fujitsu.com>
Cc: "linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"matt.fleming@intel.com" <matt.fleming@intel.com>,
"jlee@suse.com" <jlee@suse.com>,
"matt@console-pimps.org" <matt@console-pimps.org>,
"richard@nod.at" <richard@nod.at>,
"cxie@redhat.com" <cxie@redhat.com>
Subject: Re: [PATCH] x86, efi: add no_bricked_efi whitelist
Date: Wed, 20 Nov 2013 16:02:57 +0000 [thread overview]
Message-ID: <1384963376.20536.3.camel@x230> (raw)
In-Reply-To: <528C740A.6010407@jp.fujitsu.com>
On Wed, 2013-11-20 at 17:34 +0900, Yasuaki Ishimatsu wrote:
> When booting my system, remaining space of efi variable storage is about
> 5KB. So there is no room that sets a new variable to the storage. On my
> system, trigger of gc is when EFI_OUT_OF_RESOURCES occurs on pre OS
> environment with UEFI. So if EFI_OUT_OF_RESOURCES occurs by the 5Kbyte
> threshold, nvram storage cannot be used until EFI_OUT_OF_RESOURCES occurs
> on pre OS environment with UEFI.
By "remaining space is about 5KB", do you mean that the rest of the
space is filled with variables or do you mean that there is more free
space but it hasn't been garbage collected?
--
Matthew Garrett <matthew.garrett@nebula.com>
next prev parent reply other threads:[~2013-11-20 16:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 8:34 [PATCH] x86, efi: add no_bricked_efi whitelist Yasuaki Ishimatsu
[not found] ` <528C740A.6010407-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2013-11-20 8:54 ` Richard Weinberger
2013-11-21 9:25 ` Yasuaki Ishimatsu
2013-11-20 16:02 ` Matthew Garrett [this message]
2013-11-21 9:35 ` Yasuaki Ishimatsu
[not found] ` <528DD3E0.3050606-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2013-11-21 20:12 ` Matthew Garrett
2013-11-22 0:00 ` Yasuaki Ishimatsu
[not found] ` <528E9EB2.3060808-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2013-11-22 0:03 ` Matthew Garrett
2013-11-22 6:23 ` Yasuaki Ishimatsu
[not found] ` <528EF87D.4050300-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2013-11-22 6:29 ` [PATCH] x86, efi: add efi_whitelist_table to use all efi variable storage Yasuaki Ishimatsu
2013-11-22 17:47 ` Matthew Garrett
2013-12-03 3:20 ` Yasuaki Ishimatsu
[not found] ` <529D4DF5.80502-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2013-12-03 3:45 ` Matthew Garrett
[not found] ` <25e63f3b748741998d2b3e04bbc53064-jH1ztPcg5hENpgVgjDfI3Wu6+pknBqLbXA4E9RH9d+qIuWR1G4zioA@public.gmane.org>
2013-12-03 4:49 ` Yasuaki Ishimatsu
2013-12-03 5:04 ` Matthew Garrett
[not found] ` <20131203050450.GA30967-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2013-12-03 5:12 ` Yasuaki Ishimatsu
2013-11-22 17:48 ` [PATCH] x86, efi: add no_bricked_efi whitelist Matthew Garrett
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=1384963376.20536.3.camel@x230 \
--to=matthew.garrett@nebula.com \
--cc=cxie@redhat.com \
--cc=isimatu.yasuaki@jp.fujitsu.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=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;
as well as URLs for NNTP newsgroup(s).