linux-efi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Garrett <matthew.garrett-05XSO3Yj/JvQT0dZR+AlfA@public.gmane.org>
To: "isimatu.yasuaki-+CUm20s59erQFUHtdCDX3A@public.gmane.org"
	<isimatu.yasuaki-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
Cc: "linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org"
	<matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"jlee-IBi9RG/b67k@public.gmane.org"
	<jlee-IBi9RG/b67k@public.gmane.org>,
	"matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org"
	<matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>,
	"richard-/L3Ra7n9ekc@public.gmane.org"
	<richard-/L3Ra7n9ekc@public.gmane.org>,
	"cxie-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
	<cxie-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] x86, efi: add no_bricked_efi whitelist
Date: Fri, 22 Nov 2013 00:03:53 +0000	[thread overview]
Message-ID: <1385078632.12107.3.camel@x230> (raw)
In-Reply-To: <528E9EB2.3060808-+CUm20s59erQFUHtdCDX3A@public.gmane.org>

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@nebula.com>

  parent reply	other threads:[~2013-11-22  0:03 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
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 [this message]
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=1385078632.12107.3.camel@x230 \
    --to=matthew.garrett-05xso3yj/jvqt0dzr+alfa@public.gmane.org \
    --cc=cxie-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=isimatu.yasuaki-+CUm20s59erQFUHtdCDX3A@public.gmane.org \
    --cc=jlee-IBi9RG/b67k@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org \
    --cc=matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=richard-/L3Ra7n9ekc@public.gmane.org \
    /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).