From: joeyli <jlee@suse.com>
To: Matt Fleming <matt.fleming@intel.com>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
glin@suse.com, Jeremy Kerr <jeremy.kerr@canonical.com>,
Matthew Garrett <mjg@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>, Peter Jones <pjones@redhat.com>
Subject: Re: [PATCH] efi: add efivars kobject to efi sysfs folder
Date: Thu, 04 Oct 2012 17:46:24 +0800 [thread overview]
Message-ID: <1349343984.24232.147.camel@linux-s257.site> (raw)
In-Reply-To: <1349340875.15966.18.camel@mfleming-mobl1.ger.corp.intel.com>
於 四,2012-10-04 於 09:54 +0100,Matt Fleming 提到:
> On Thu, 2012-10-04 at 10:24 +0800, Lee, Chun-Yi wrote:
> > UEFI variable filesystem need a new mount point, so this patch add
> > efivars kobject to efi_kobj for create a /sys/firmware/efi/efivars
> > folder.
> >
> > Cc: Matt Fleming <matt.fleming@intel.com>
> > Cc: Jeremy Kerr <jeremy.kerr@canonical.com>
> > Cc: Matthew Garrett <mjg@redhat.com>
> > Cc: H. Peter Anvin <hpa@zytor.com>
> > Signed-off-by: Lee, Chun-Yi <jlee@suse.com>
> > ---
> > drivers/firmware/efivars.c | 11 +++++++++++
> > include/linux/efi.h | 1 +
> > 2 files changed, 12 insertions(+), 0 deletions(-)
>
> Actually, shouldn't the new filesystem be called "efivarfs", or "efifs"
> to make it more explicit that it is a filesystem?
I used "efivars" because this folder generated by efivars. But, I like
your suggestion for use "efivarfs", it's better then "efivars".
>
> We also need something in Documentation/filesystems/ describing the old
> EFI variable method, why it's no longer any good, and why the new
> filesystem is favoured. Does anybody have anything to add to the
> following?
>
> diff --git a/Documentation/filesystems/00-INDEX b/Documentation/filesystems/00-INDEX
> index 8c624a1..ddf5a83 100644
> --- a/Documentation/filesystems/00-INDEX
> +++ b/Documentation/filesystems/00-INDEX
> @@ -38,6 +38,8 @@ dnotify_test.c
> - example program for dnotify
> ecryptfs.txt
> - docs on eCryptfs: stacked cryptographic filesystem for Linux.
> +efivars.txt
> + - info for the efivars filesystem.
> exofs.txt
> - info, usage, mount options, design about EXOFS.
> ext2.txt
> diff --git a/Documentation/filesystems/efivars.txt b/Documentation/filesystems/efivars.txt
> new file mode 100644
> index 0000000..4350c1a
> --- /dev/null
> +++ b/Documentation/filesystems/efivars.txt
> @@ -0,0 +1,16 @@
> +
> +efivars - a (U)EFI variable filesystem
> +
> +The efivars filesystem was created to address the shortcomings of
> +using entries in sysfs to maintain EFI variables. The old sysfs EFI
> +variables code only supported 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.
> +
> +Variables can be created, deleted and modified with the efivars
> +filesystem.
> +
> +The efivars filesystem is typically mounted like this,
> +
> + mount -t efivars none /sys/firmware/efi/efivars
>
The above documentation is really good!
Thanks a lot!
Joey Lee
prev parent reply other threads:[~2012-10-04 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 2:24 [PATCH] efi: add efivars kobject to efi sysfs folder Lee, Chun-Yi
2012-10-04 8:54 ` Matt Fleming
2012-10-04 9:08 ` Jeremy Kerr
2012-10-04 13:30 ` Peter Jones
2012-10-04 9:46 ` joeyli [this message]
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=1349343984.24232.147.camel@linux-s257.site \
--to=jlee@suse.com \
--cc=glin@suse.com \
--cc=hpa@zytor.com \
--cc=jeremy.kerr@canonical.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--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 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).