All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Walle <bwalle@suse.de>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: x86@kernel.org, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org, vgoyal@redhat.com
Subject: Re: [PATCH 3/3] Limit E820 map when a user-defined memory map is specified
Date: Tue, 24 Jun 2008 16:07:29 +0200	[thread overview]
Message-ID: <20080624160729.2bead69c@halley.suse.de> (raw)
In-Reply-To: <86802c440806221311q5a65cdb6me24b45de5657359c@mail.gmail.com>

* Yinghai Lu [2008-06-22 13:11]:
>
> On Sun, Jun 22, 2008 at 12:56 PM, Bernhard Walle <bwalle@suse.de> wrote:
> > * "Yinghai Lu" <yhlu.kernel@gmail.com> [2008-06-20 13:34]:
> >>
> >> any problem that you encountered without this patch?
> >
> > Sorry, forgot to answer that question.
> >
> > Yes, if you use mem=3G and take a dump, kexec builds the ELF core
> > headers for the full memory size, which means that the dump is as large
> > as the physical memory of the machine is, which doesn't make sense.
> 
> can we use e820_update_range instead? so e820_setup_gap still can get
> correct value?

Yes, good idea. Patch is in the queue ...


Bernhard
-- 
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Bernhard Walle <bwalle@suse.de>
To: "Yinghai Lu" <yhlu.kernel@gmail.com>
Cc: x86@kernel.org, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org, vgoyal@redhat.com
Subject: Re: [PATCH 3/3] Limit E820 map when a user-defined memory map is specified
Date: Tue, 24 Jun 2008 16:07:29 +0200	[thread overview]
Message-ID: <20080624160729.2bead69c@halley.suse.de> (raw)
In-Reply-To: <86802c440806221311q5a65cdb6me24b45de5657359c@mail.gmail.com>

* Yinghai Lu [2008-06-22 13:11]:
>
> On Sun, Jun 22, 2008 at 12:56 PM, Bernhard Walle <bwalle@suse.de> wrote:
> > * "Yinghai Lu" <yhlu.kernel@gmail.com> [2008-06-20 13:34]:
> >>
> >> any problem that you encountered without this patch?
> >
> > Sorry, forgot to answer that question.
> >
> > Yes, if you use mem=3G and take a dump, kexec builds the ELF core
> > headers for the full memory size, which means that the dump is as large
> > as the physical memory of the machine is, which doesn't make sense.
> 
> can we use e820_update_range instead? so e820_setup_gap still can get
> correct value?

Yes, good idea. Patch is in the queue ...


Bernhard
-- 
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development

  reply	other threads:[~2008-06-24 14:06 UTC|newest]

Thread overview: 44+ 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 [this message]
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
2008-06-20 20:35     ` H. Peter Anvin
2008-06-22 19:59     ` Bernhard Walle
2008-06-22 19:59       ` Bernhard Walle
  -- strict thread matches above, loose matches on Subject: below --
2008-06-24 14:35 Limit E820 map when specifying mem parameter Bernhard Walle
2008-06-24 14:35 ` [PATCH 3/3] Limit E820 map when a user-defined memory map is specified Bernhard Walle
2008-06-24 20:03   ` Yinghai Lu
2008-06-25 12:02 Limit E820 map when specifying mem parameter Bernhard Walle
2008-06-25 12:02 ` [PATCH 3/3] Limit E820 map when a user-defined memory map is specified Bernhard Walle
2008-06-25 12:02   ` Bernhard Walle
2008-06-25 16:01   ` Yinghai Lu
2008-06-25 16:01     ` Yinghai Lu
2008-06-25 16:03     ` Bernhard Walle
2008-06-25 16:03       ` Bernhard Walle
2008-06-25 16:58       ` Yinghai Lu
2008-06-25 16:58         ` Yinghai Lu
2008-06-25 19:39         ` Bernhard Walle
2008-06-25 19:39           ` 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=20080624160729.2bead69c@halley.suse.de \
    --to=bwalle@suse.de \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@redhat.com \
    --cc=x86@kernel.org \
    --cc=yhlu.kernel@gmail.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 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.