public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Sourav Sen <souravs@india.hp.com>
Cc: Matt_Domsch@dell.com, matthew.e.tolentino@intel.com,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6.6 PATCH] Exposing EFI memory map
Date: Fri, 07 May 2004 21:49:03 +0000	[thread overview]
Message-ID: <20040507214903.GE13511@kroah.com> (raw)
In-Reply-To: <006901c43418$095436f0$39624c0f@india.hp.com>

On Fri, May 07, 2004 at 03:15:30PM +0530, Sourav Sen wrote:
> Here we have "Array of values of same types". And it does not do much
> nifty formatting either. Is that not acceptable?

But they are not of the same time, as you admitted :)

Also, they could be bigger than a single page, right?  That is not
possible right now in sysfs.

> If that is not, how about the following.
> 
> 	1. Create a directory "memmap" under firmware/efi/
> 	2. Create files "map_start", "map_size" and "mapdesc_size" under
>          that exposing ia64_boot_param->efi_memmap,
> ia64_boot_param->efi_memmap_size
> 	   and ia64_boot_param->efi_memdesc_size respectively.
> 
> Userland can make meaning out of them by knowing the values and knowing
> about "efi_memory_desc_t" which is already there in
> /usr/include/asm/efi.h

I think you should address the other issues in this thread before
worrying about the sysfs interface (why have this at all, incorrect
data for hotplug mem, etc.)

> PS: BTW, Your slides on "Dealing with the Linux Kernel Community" at:
> http://www.kroah.com/linux/talks/cgl_talk_2002_10_16/mgp00001.html
> is kind of useful to me. This is my first time :-)

If only more people/companies would heed those rules...

thanks,

greg k-h

  reply	other threads:[~2004-05-07 21:49 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-06  8:53 [2.6.6 PATCH] Exposing EFI memory map Sourav Sen
2004-05-06  9:30 ` Sourav Sen
2004-05-06 10:44 ` Christoph Hellwig
2004-05-06 11:59   ` Matthew Wilcox
2004-05-06 12:18     ` Arjan van de Ven
2004-05-06 13:27       ` Matthew Wilcox
2004-05-06 14:00         ` Dave Hansen
2004-05-06 14:09           ` Arjan van de Ven
2004-05-06 14:09     ` Christoph Hellwig
2004-05-06 12:46 ` Matt Domsch
2004-05-06 13:23 ` Luck, Tony
2004-05-06 13:32 ` Sourav Sen
2004-05-06 15:08   ` Bjorn Helgaas
2004-05-06 16:14 ` Tolentino, Matthew E
2004-05-06 16:37 ` Sourav Sen
2004-05-06 16:49   ` Dave Hansen
2004-05-06 16:40 ` Greg KH
2004-05-06 18:47 ` Tolentino, Matthew E
2004-05-06 18:57   ` Dave Hansen
2004-05-06 20:54 ` Tolentino, Matthew E
2004-05-06 21:44   ` [Lhms-devel] " Dave Hansen
2004-05-07  9:57 ` Sourav Sen
2004-05-07 21:49   ` Greg KH [this message]
2004-05-11 14:56 ` Sourav Sen
2004-05-11 15:42   ` Dave Hansen
2004-05-12 10:36 ` Sourav Sen
2004-05-12 16:15   ` Dave Hansen
2004-05-13 14:22 ` Sourav Sen
2004-05-13 15:32   ` Dave Hansen

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=20040507214903.GE13511@kroah.com \
    --to=greg@kroah.com \
    --cc=Matt_Domsch@dell.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.e.tolentino@intel.com \
    --cc=souravs@india.hp.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