From: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
Cc: matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org,
greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
horms-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org
Subject: Re: split efi systab in sysfs
Date: Thu, 26 Dec 2013 10:17:06 +0800 [thread overview]
Message-ID: <20131226021705.GC3750@dhcp-16-126.nay.redhat.com> (raw)
In-Reply-To: <20131226021238.GB3750-je1gSBvt1TcFLmT5oZ11vB/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
CCing Simon and kexec list
On 12/26/13 at 10:12am, Dave Young wrote:
> On 12/25/13 at 05:55pm, H. Peter Anvin wrote:
> > On 12/25/2013 05:53 PM, Dave Young wrote:
> > > Hi, Matt and Peter
> > >
> > > Currently /sys/firmware/efi/systab contains multi-lines for efi systab
> > > entries. As previous discussion with Greg, this is not a good in sysfs.
> > > I wonder if there's other users for this file except kexec-tools.
> > >
> > > If kexec-tools is the only user, maybe I can split it as several files.
> > > In kexec-tools just use /sys/firmware/efi/"$entry_name" and if $entry_name
> > > does not exist then switch to old systab file.
> > >
> >
> > Yes, the sysfs standard is "one entry per datum". I have no idea about
> > who the user(s) might be, though.
>
> Even the only known user kexec-tools, for new kernel + old kexec-tools we
> have no way to support, maybe this systab should be kept forever...
prev parent reply other threads:[~2013-12-26 2:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-26 1:53 split efi systab in sysfs Dave Young
[not found] ` <20131226015308.GA3750-je1gSBvt1TcFLmT5oZ11vB/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2013-12-26 1:55 ` H. Peter Anvin
2013-12-26 2:12 ` Dave Young
[not found] ` <20131226021238.GB3750-je1gSBvt1TcFLmT5oZ11vB/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2013-12-26 2:17 ` Dave Young [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=20131226021705.GC3750@dhcp-16-126.nay.redhat.com \
--to=dyoung-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org \
--cc=horms-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org \
--cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
--cc=kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@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 \
/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