public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: Andi Kleen <ak@suse.de>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	akpm@linux-foundation.org, Yinghai Lu <yhlu.kernel@gmail.com>,
	Chandramouli Narayanan <mouli@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm -v4 0/3] i386/x86_64 boot: 32-bit boot protocol
Date: Tue, 09 Oct 2007 18:08:05 -0700	[thread overview]
Message-ID: <470C25F5.1020202@zytor.com> (raw)
In-Reply-To: <1191978236.9719.101.camel@caritas-dev.intel.com>

Huang, Ying wrote:
> On Tue, 2007-10-09 at 12:23 -0700, H. Peter Anvin wrote:
>> Huang, Ying wrote:
>>> - Which fields of boot parameters should be exported directly in
>>>   sysfs? Export all fields of boot parameters in sysfs is too complex
>>>   and unnecessary. Which fields should be?
>>>
>> The main this is that since this is a fixed-format, ABI-defined 
>> structure, regardless of individual fields it should be exported as a 
>> binary object.  That is also the only way to deal with a kernel which 
>> may not itself know about specific items making the data available to 
>> other users, like kexec.
>>
>> It's not clear to me from reading the code what model you're using for 
>> exporting this data in sysfs.  Could you describe it in some detail?
>>
>> What I had envisioned would be an object for the boot_params structure 
>> and a systematic object for each linked-list object, at a very minimum.
>>
> 
> OK. The directory structure is as follow:
> 
> + sys + kernel + boot_params - version			/* version of boot protocol */
>                              - data			/* binary file of boot_params */
>                              + setup_data + 0 - type	/* type id of setup_data 0 */
>                                               - data	/* binary file of setup_data 0 */
>                                           + 1 - type	/* type id of setup_data 1 */
>                                               - data	/* binary file of setup_data 1 */
>                                           + 2 - type
>                                               - data
>                                           ...
> 

Looks good to me.

	-hpa

      reply	other threads:[~2007-10-10  1:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-09  6:40 [PATCH -mm -v4 0/3] i386/x86_64 boot: 32-bit boot protocol Huang, Ying
2007-10-09 19:23 ` H. Peter Anvin
2007-10-10  1:03   ` Huang, Ying
2007-10-10  1:08     ` H. Peter Anvin [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=470C25F5.1020202@zytor.com \
    --to=hpa@zytor.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mouli@linux.intel.com \
    --cc=yhlu.kernel@gmail.com \
    --cc=ying.huang@intel.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