public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Problem with elilo 3.3a
Date: Fri, 14 Feb 2003 07:09:03 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805849@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805846@msgid-missing>

>>>>> On Thu, 13 Feb 2003 22:58:53 -0800, Stephane Eranian <eranian@frankl.hpl.hp.com> said:

  Stephane> Note that the memory map itself IS NOT allocated inside
  Stephane> the boot_param structure. This structure only contains a
  Stephane> pointer to it as well as the size of the region. The map
  Stephane> is dynamically allocated (in util.c).  The kernel
  Stephane> (arch/ia64/kernel/setup.c) assumes all "valid" memory
  Stephane> regions are free except for regions it knows about which
  Stephane> are: - the boot param struct - the memory map (address in
  Stephane> size in boot param struct) - initrd - command line string
  Stephane> - kernel code and data

That's not good.  The kernel assumes that the efi_memmap was copied
and happily scribbles over it.  I thought the bootloader used to make
a copy of the mem-map.  Am I misremembering?

	--david


  parent reply	other threads:[~2003-02-14  7:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-14  3:15 [Linux-ia64] Problem with elilo 3.3a Sluder, Charles
2003-02-14  6:58 ` Stephane Eranian
2003-02-14  7:09 ` David Mosberger [this message]
2003-02-14  7:28 ` Stephane Eranian
2003-02-14  7:34 ` David Mosberger
2003-02-14 18:33 ` Sluder, Charles
2003-02-15  6:28 ` Sluder, Charles
2003-02-18 18:23 ` Stephane Eranian

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=marc-linux-ia64-105590709805849@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.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