From: "H. Peter Anvin" <hpa@zytor.com>
To: Dave Young <dyoung@redhat.com>, Greg KH <greg@kroah.com>
Cc: mjg59@srcf.ucam.org, linux-efi@vger.kernel.org,
Toshi Kani <toshi.kani@hp.com>,
x86@kernel.org, kexec@lists.infradead.org,
James.Bottomley@HansenPartnership.com, horms@verge.net.au,
bp@alien8.de, ebiederm@xmission.com,
Ingo Molnar <mingo@kernel.org>,
vgoyal@redhat.com
Subject: Re: [patch 1/3 v2] Add function get_bootparam
Date: Sun, 17 Nov 2013 19:29:06 -0800 [thread overview]
Message-ID: <52898982.3020200@zytor.com> (raw)
In-Reply-To: <20131118022234.GD4025@dhcp-16-126.nay.redhat.com>
On 11/17/2013 06:22 PM, Dave Young wrote:
> On 11/13/13 at 08:50am, Dave Young wrote:
>> On 11/12/13 at 06:51pm, Greg KH wrote:
>>> On Tue, Nov 12, 2013 at 01:37:25AM -0800, H. Peter Anvin wrote:
>>>> On 11/12/2013 12:30 AM, Greg KH wrote:
>>>>>
>>>>> And these binary data blobs are a "standard" somewhere, and will not
>>>>> change per kernel version change?
>>>>>
>>>>> If so, that structure is fine with me.
>>>>>
>>>>
>>>> Correct. The structure is documented in Documentation/x86/boot.txt, and
>>>> has been largely invariant (but extended) since the beginning of Linux.
>>>> It has sometimes taken some serious work to keep it that way.
>>>
>>> Ok, then use the binary sysfs file interface for these blobs, and
>>> everyone will be happy.
>>
>> Since we got an agreement I will move them to sysfs in next version.
>
> I have created one patch for the sysfs part this weekend, bug I'm hesitating to
> remove the debugfs part because currently there's already user, I tend to
> keep them in debugfs for now.
>
> What do you think, Peter?
>
Yes, it makes sense to keep them for compatibility, at least for now.
What is the specific user that already exists?
-hpa
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
To: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Greg KH <greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
Cc: mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Toshi Kani <toshi.kani-VXdhtT5mjnY@public.gmane.org>,
x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org,
horms-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org,
bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org,
ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org,
Ingo Molnar <mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: [patch 1/3 v2] Add function get_bootparam
Date: Sun, 17 Nov 2013 19:29:06 -0800 [thread overview]
Message-ID: <52898982.3020200@zytor.com> (raw)
In-Reply-To: <20131118022234.GD4025-je1gSBvt1TcFLmT5oZ11vB/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
On 11/17/2013 06:22 PM, Dave Young wrote:
> On 11/13/13 at 08:50am, Dave Young wrote:
>> On 11/12/13 at 06:51pm, Greg KH wrote:
>>> On Tue, Nov 12, 2013 at 01:37:25AM -0800, H. Peter Anvin wrote:
>>>> On 11/12/2013 12:30 AM, Greg KH wrote:
>>>>>
>>>>> And these binary data blobs are a "standard" somewhere, and will not
>>>>> change per kernel version change?
>>>>>
>>>>> If so, that structure is fine with me.
>>>>>
>>>>
>>>> Correct. The structure is documented in Documentation/x86/boot.txt, and
>>>> has been largely invariant (but extended) since the beginning of Linux.
>>>> It has sometimes taken some serious work to keep it that way.
>>>
>>> Ok, then use the binary sysfs file interface for these blobs, and
>>> everyone will be happy.
>>
>> Since we got an agreement I will move them to sysfs in next version.
>
> I have created one patch for the sysfs part this weekend, bug I'm hesitating to
> remove the debugfs part because currently there's already user, I tend to
> keep them in debugfs for now.
>
> What do you think, Peter?
>
Yes, it makes sense to keep them for compatibility, at least for now.
What is the specific user that already exists?
-hpa
next prev parent reply other threads:[~2013-11-18 3:30 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 8:29 [patch 0/3 v2] kexec-tools: efi runtime support dyoung
2013-11-05 8:29 ` dyoung-H+wXaHxf7aLQT0dZR+AlfA
2013-11-05 8:29 ` [patch 1/3 v2] Add function get_bootparam dyoung
2013-11-05 8:29 ` dyoung-H+wXaHxf7aLQT0dZR+AlfA
2013-11-12 1:27 ` Toshi Kani
2013-11-12 1:27 ` Toshi Kani
2013-11-12 2:14 ` Dave Young
2013-11-12 2:14 ` Dave Young
2013-11-12 3:20 ` H. Peter Anvin
2013-11-12 3:20 ` H. Peter Anvin
2013-11-12 3:53 ` Ingo Molnar
2013-11-12 3:53 ` Ingo Molnar
[not found] ` <aa0ccca4-b27b-41b6-8adb-3c969eb29bf7@email.android.com>
2013-11-12 14:26 ` Vivek Goyal
2013-11-12 14:26 ` Vivek Goyal
2013-11-12 7:58 ` Greg KH
2013-11-12 7:58 ` Greg KH
2013-11-12 8:08 ` Dave Young
2013-11-12 8:08 ` Dave Young
2013-11-12 8:30 ` Greg KH
2013-11-12 8:30 ` Greg KH
2013-11-12 8:50 ` Dave Young
2013-11-12 8:50 ` Dave Young
2013-11-12 9:37 ` H. Peter Anvin
2013-11-12 9:37 ` H. Peter Anvin
2013-11-12 9:51 ` Greg KH
2013-11-12 9:51 ` Greg KH
2013-11-13 0:50 ` Dave Young
2013-11-13 0:50 ` Dave Young
2013-11-18 2:22 ` Dave Young
2013-11-18 2:22 ` Dave Young
2013-11-18 3:29 ` H. Peter Anvin [this message]
2013-11-18 3:29 ` H. Peter Anvin
2013-11-18 5:29 ` Dave Young
2013-11-18 5:29 ` Dave Young
2013-11-18 5:36 ` H. Peter Anvin
2013-11-18 5:36 ` H. Peter Anvin
2013-11-05 8:29 ` [patch 2/3 v2] Add efi_info in x86 setup header dyoung
2013-11-05 8:29 ` dyoung-H+wXaHxf7aLQT0dZR+AlfA
2013-11-05 8:29 ` [patch 3/3 v2] Passing efi related data via setup_data dyoung
2013-11-05 8:29 ` dyoung-H+wXaHxf7aLQT0dZR+AlfA
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=52898982.3020200@zytor.com \
--to=hpa@zytor.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bp@alien8.de \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=greg@kroah.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=toshi.kani@hp.com \
--cc=vgoyal@redhat.com \
--cc=x86@kernel.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 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.