public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Greg KH <greg@kroah.com>
Cc: "Huang, Ying" <ying.huang@intel.com>,
	akpm@linux-foundation.org, Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Andi Kleen <ak@suse.de>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm -v3] x86 boot : export boot_params via sysfs
Date: Fri, 14 Dec 2007 11:00:28 -0800	[thread overview]
Message-ID: <4762D2CC.1030109@zytor.com> (raw)
In-Reply-To: <4762C78D.9080107@zytor.com>

H. Peter Anvin wrote:
> Greg KH wrote:
>>
>> But it ignored the fact that I said I didn't want this binary file in
>> sysfs :)
>>
>> Please take Eric's suggestion and split it up into the different pieces.
>> Some of the fields can be binary files, as they come directly from the
>> firmware, but the others should be text.
>>
> 
> But PLEASE include the full structure as a ready-to-eat object.  PLEASE.
> 

I should clarify this.

By all means go ahead and provide broken-out fields where it makes 
sense.  However:

- this *IS* a structure defined by protocol, and which, for all users 
except the 16-bit entry, comes from outside the kernel (bootloader or 
firmware.)

- a newer kernel version can add fields to this structure, but can never 
remove them.  This would cause a potential information loss if the 
current kernel doesn't have all fields available.

- the binary structure is the format that the majority of users will need.

This is directly analogous to how we treat identity information in IDE, 
or PCI configuration space -- some fields are pre-digested, but the 
entire raw information is also available.

	-hpa

  reply	other threads:[~2007-12-14 19:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-14  8:16 [PATCH -mm -v3] x86 boot : export boot_params via sysfs Huang, Ying
2007-12-14 15:52 ` Greg KH
2007-12-14 18:12   ` H. Peter Anvin
2007-12-14 19:00     ` H. Peter Anvin [this message]
2007-12-18  4:34       ` Eric W. Biederman
2007-12-18  7:29         ` Huang, Ying

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=4762D2CC.1030109@zytor.com \
    --to=hpa@zytor.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --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