linux-efi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
To: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Ard Biesheuvel
	<ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
	leif.lindholm-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH] efi: remove UEFIv2.5 properties table from /sys/firmware/efi/systab
Date: Sat, 10 Oct 2015 18:03:13 +0100	[thread overview]
Message-ID: <20151010170313.GB2723@codeblueprint.co.uk> (raw)
In-Reply-To: <20151001031505.GA8264-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>

On Thu, 01 Oct, at 11:15:05AM, Dave Young wrote:
> On 09/30/15 at 04:43pm, Ard Biesheuvel wrote:
> > As pointed out by Dave Young, /sys/firmware/efi/systab violates the
> > sysfs one-value-per-file policy already, so adding more data items
> > to it should be avoided. So let's remove the PROP= line that lists
> > the address of the recently introduced Properties Table before it
> > appears in a release.
> > 
> > Signed-off-by: Ard Biesheuvel <ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
> > ---
> > 
> > Matt pointed out that there still needs to be a way for kexec/x86 to
> > access this data, since it needs to pass it on to the kexec kernel.
> > That is way out of my area of expertise, so I will leave it to you
> > to come up with something suitable there.
> > 
> >  drivers/firmware/efi/efi.c | 2 --
> >  1 file changed, 2 deletions(-)
> > 
> > diff --git a/drivers/firmware/efi/efi.c b/drivers/firmware/efi/efi.c
> > index 2eb31e28a35c..3804ecd4a77a 100644
> > --- a/drivers/firmware/efi/efi.c
> > +++ b/drivers/firmware/efi/efi.c
> > @@ -109,8 +109,6 @@ static ssize_t systab_show(struct kobject *kobj,
> >  		str += sprintf(str, "BOOTINFO=0x%lx\n", efi.boot_info);
> >  	if (efi.uga != EFI_INVALID_TABLE_ADDR)
> >  		str += sprintf(str, "UGA=0x%lx\n", efi.uga);
> > -	if (efi.properties_table != EFI_INVALID_TABLE_ADDR)
> > -		str += sprintf(str, "PROP=0x%lx\n", efi.properties_table);
> >  
> >  	return str - buf;
> >  }
> 
> Ard, thanks, it looks good to me.
> 
> Acked-by: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

Thanks guys. I've folded this into the existing properties table patch
from Ard, because there's no sense in having it as a separate patch
and since that would make backporting more difficult.

-- 
Matt Fleming, Intel Open Source Technology Center

      parent reply	other threads:[~2015-10-10 17:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30 14:43 [PATCH] efi: remove UEFIv2.5 properties table from /sys/firmware/efi/systab Ard Biesheuvel
     [not found] ` <1443624196-31630-1-git-send-email-ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-10-01  3:15   ` Dave Young
     [not found]     ` <20151001031505.GA8264-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2015-10-10 17:03       ` Matt Fleming [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=20151010170313.GB2723@codeblueprint.co.uk \
    --to=matt-mf/unelci9gs6ibeejttw/xrex20p6io@public.gmane.org \
    --cc=ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=leif.lindholm-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=matt.fleming-ral2JQCrhuEAvxtiuMwx3w@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).