All of lore.kernel.org
 help / color / mirror / Atom feed
From: joeyli <jlee@suse.com>
To: jeremy.kerr@canonical.com, Matthew Garrett <mjg@redhat.com>
Cc: linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Matt Domsch <Matt_Domsch@Dell.com>,
	Peter Jones <pjones@redhat.com>
Subject: Re: Fwd: [RFC,PATCH v2] efi: Add support for a UEFI variable filesystem
Date: Thu, 13 Sep 2012 16:08:07 +0800	[thread overview]
Message-ID: <1347523687.596.29.camel@linux-s257.site> (raw)
In-Reply-To: <CAGLnvc9BXAW8F8WWyDxuF1_J+0np3uqUBmknuJewOJHhe-mxvw@mail.gmail.com>

On Thu, 2012-09-06 at 13:40 +0800, Jeremy Kerr wrote:
> From: Matthew Garrett <mjg@redhat.com>
> 
> The existing EFI variables code only supports variables of up to 1024
> bytes. This limitation existed in version 0.99 of the EFI
> specification,
> but was removed before any full releases. Since variables can now be
> larger than a single page, sysfs isn't the best interface for this.
> So,
> instead, let's add a filesystem. Variables can be read, written and
> created, with the first 4 bytes of each variable representing its UEFI
> attributes. The create() method doesn't actually commit to flash since
> zero-length variables can't exist per-spec.
> 
> Updates from Jeremy Kerr <jeremy.kerr@canonical.com>.
> 
> Signed-off-by: Matthew Garrett <mjg@redhat.com>
> Signed-off-by: Jeremy Kerr <jeremy.kerr@canonical.com>
> 
> ---
> v2: Add check for < 4-byte writes
> 

Do we have plan to create a new kobject add to /sys/firmware/efi for
provide a fixed mount point to efivars fs?
e.g. /sys/firmware/efi/efivars

Or we just direct reuse current /sys/firmeware/efi/vars? But, that means
we need think for the backward compatibility if choice reuse vars
folder.


Thanks a lot!
Joey Lee


  parent reply	other threads:[~2012-09-13  8:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06  5:40 [RFC,PATCH v2] efi: Add support for a UEFI variable filesystem Jeremy Kerr
2012-09-06 14:18 ` Matt Fleming
2012-09-06 14:23   ` Jeremy Kerr
2012-09-06 14:30     ` Matt Fleming
2012-09-06 14:37       ` Jeremy Kerr
2012-09-06 14:46         ` Matt Fleming
     [not found] ` <CAGLnvc9BXAW8F8WWyDxuF1_J+0np3uqUBmknuJewOJHhe-mxvw@mail.gmail.com>
2012-09-13  8:08   ` joeyli [this message]
2012-09-13  8:10   ` joeyli
2012-09-13 13:52     ` Peter Jones
2012-09-14  3:45       ` joeyli
2012-09-14  4:41         ` H. Peter Anvin
2012-09-15  2:44           ` joeyli
2012-09-15  2:26   ` 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=1347523687.596.29.camel@linux-s257.site \
    --to=jlee@suse.com \
    --cc=Matt_Domsch@Dell.com \
    --cc=hpa@zytor.com \
    --cc=jeremy.kerr@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=pjones@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.