[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1385078632.12107.3.camel@x230>
Date: Fri, 22 Nov 2013 00:03:53 +0000
From: Matthew Garrett <matthew.garrett@...ula.com>
To: "isimatu.yasuaki@...fujitsu.com" <isimatu.yasuaki@...fujitsu.com>
CC: "linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"matt.fleming@...el.com" <matt.fleming@...el.com>,
"jlee@...e.com" <jlee@...e.com>,
"matt@...sole-pimps.org" <matt@...sole-pimps.org>,
"richard@....at" <richard@....at>,
"cxie@...hat.com" <cxie@...hat.com>
Subject: Re: [PATCH] x86, efi: add no_bricked_efi whitelist
On Fri, 2013-11-22 at 09:00 +0900, Yasuaki Ishimatsu wrote:
> (2013/11/22 5:12), Matthew Garrett wrote:
> > On Thu, 2013-11-21 at 18:35 +0900, Yasuaki Ishimatsu wrote:
> >
> >> Remaining space is free space that can be used by efi variable. But by 5KB
> >> threshold, we cannot use the space while running OS.
> >
> > Is the situation something like(assuming a 128KB flash part):
> >
> > 1) 64KB of variables, 59KB of deleted variables, 5KB of free space,
>
> My situation looks like this. The free space spreads out if gc runs.
Ok. In that case Joey's suggestion that we try forcing a GC run in the
boot stub if free space < (threshold * 2) might be the best plan.
--
Matthew Garrett <matthew.garrett@...ula.com>
Powered by blists - more mailing lists