public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Bernhard Walle <bwalle@suse.de>
Cc: kexec@lists.infradead.org, x86@kernel.org,
	linux-kernel@vger.kernel.org, vgoyal@redhat.com,
	Greg KH <greg@kroah.com>
Subject: Re: [PATCH 2/3] Use /proc/firmware_mem for x86 (e820)
Date: Tue, 24 Jun 2008 20:28:17 +0200	[thread overview]
Message-ID: <20080624182817.GI5642@ucw.cz> (raw)
In-Reply-To: <1213977420-1555-3-git-send-email-bwalle@suse.de>

Hi!

> This patch copies the E820 map very early, before the kernel applies various
> operations. That copy is used later to register only the BIOS-provided E820
> map later in the resource tree for /proc/firmware_mem.

It is not process related -> it should not go to /proc. Talk to Greg.

							Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2008-06-26  8:21 UTC|newest]

Thread overview: 16+ 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 ` [PATCH 1/3] Introduce /proc/firmware_mem Bernhard Walle
2008-06-20 15:56 ` [PATCH 2/3] Use /proc/firmware_mem for x86 (e820) Bernhard Walle
2008-06-24 18:28   ` Pavel Machek [this message]
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 19:45   ` Vivek Goyal
2008-06-20 20:34   ` Yinghai Lu
2008-06-22 19:46     ` Bernhard Walle
2008-06-22 19:56     ` Bernhard Walle
2008-06-22 20:11       ` Yinghai Lu
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 19:42 ` Vivek Goyal
2008-06-20 20:35   ` H. Peter Anvin
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=20080624182817.GI5642@ucw.cz \
    --to=pavel@suse.cz \
    --cc=bwalle@suse.de \
    --cc=greg@kroah.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox