All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@kernel.org>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Bernhard Walle <bwalle@suse.de>,
	x86@kernel.org, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: Introduce userspace interface for Firmware-provided memory map
Date: Fri, 20 Jun 2008 13:35:42 -0700	[thread overview]
Message-ID: <485C149E.1000807@kernel.org> (raw)
In-Reply-To: <20080620194200.GC21235@redhat.com>

Vivek Goyal wrote:
> On Fri, Jun 20, 2008 at 05:56:57PM +0200, Bernhard Walle wrote:
>> This patch (as request for comments) introduces a new userspace interface
>> /proc/firmware_mem that provides the unfiltered view of the BIOS on
>> memory configuration. That's usable for two reasons:
> 
> How about /proc/firmware_memmap. This is little longish but probably more
> clear in intent.

Perhaps even /proc/firmware/memmap (or /sys/firmware/memmap/...).  I 
realize introducing a new directory is annoying, but it's a namespace 
that is likely to have other users.

	-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@kernel.org>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Bernhard Walle <bwalle@suse.de>,
	kexec@lists.infradead.org, x86@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Introduce userspace interface for Firmware-provided memory map
Date: Fri, 20 Jun 2008 13:35:42 -0700	[thread overview]
Message-ID: <485C149E.1000807@kernel.org> (raw)
In-Reply-To: <20080620194200.GC21235@redhat.com>

Vivek Goyal wrote:
> On Fri, Jun 20, 2008 at 05:56:57PM +0200, Bernhard Walle wrote:
>> This patch (as request for comments) introduces a new userspace interface
>> /proc/firmware_mem that provides the unfiltered view of the BIOS on
>> memory configuration. That's usable for two reasons:
> 
> How about /proc/firmware_memmap. This is little longish but probably more
> clear in intent.

Perhaps even /proc/firmware/memmap (or /sys/firmware/memmap/...).  I 
realize introducing a new directory is annoying, but it's a namespace 
that is likely to have other users.

	-hpa

  reply	other threads:[~2008-06-20 20:51 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-20 15:56 Introduce userspace interface for Firmware-provided memory map Bernhard Walle
2008-06-20 15:56 ` Bernhard Walle
2008-06-20 15:56 ` [PATCH 1/3] Introduce /proc/firmware_mem Bernhard Walle
2008-06-20 15:56   ` Bernhard Walle
2008-06-20 15:56 ` [PATCH 2/3] Use /proc/firmware_mem for x86 (e820) Bernhard Walle
2008-06-20 15:56   ` Bernhard Walle
2008-06-24 18:28   ` Pavel Machek
2008-06-24 18:28     ` Pavel Machek
2008-06-26  8:21     ` Bernhard Walle
2008-06-26  8:21       ` Bernhard Walle
2008-06-20 15:57 ` [PATCH 3/3] Limit E820 map when a user-defined memory map is specified Bernhard Walle
2008-06-20 15:57   ` Bernhard Walle
2008-06-20 19:45   ` Vivek Goyal
2008-06-20 19:45     ` Vivek Goyal
2008-06-20 20:34   ` Yinghai Lu
2008-06-20 20:34     ` Yinghai Lu
2008-06-22 19:46     ` Bernhard Walle
2008-06-22 19:46       ` Bernhard Walle
2008-06-22 19:56     ` Bernhard Walle
2008-06-22 19:56       ` Bernhard Walle
2008-06-22 20:11       ` Yinghai Lu
2008-06-22 20:11         ` Yinghai Lu
2008-06-24 14:07         ` Bernhard Walle
2008-06-24 14:07           ` Bernhard Walle
2008-06-20 15:58 ` Introduce userspace interface for Firmware-provided memory map Bernhard Walle
2008-06-20 15:58   ` Bernhard Walle
2008-06-20 19:42 ` Vivek Goyal
2008-06-20 19:42   ` Vivek Goyal
2008-06-20 20:35   ` H. Peter Anvin [this message]
2008-06-20 20:35     ` H. Peter Anvin
2008-06-22 19:59     ` Bernhard Walle
2008-06-22 19:59       ` Bernhard Walle

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=485C149E.1000807@kernel.org \
    --to=hpa@kernel.org \
    --cc=bwalle@suse.de \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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.