From: Vaibhav Sharma <vaibhav.sh@gmail.com>
To: linux-ia64@vger.kernel.org
Subject: Re: IA64 memory
Date: Thu, 03 Feb 2005 07:15:40 +0000 [thread overview]
Message-ID: <851caabb0502022303709136b@mail.gmail.com> (raw)
In-Reply-To: <851caabb05020220513945437@mail.gmail.com>
Hi,
Thanks a lot for a quick response, I appreciate.
If you could only help me out a little more ….
See, I need to change some of the boot parameters as read/seen by the
kernel. Once these parameters have been setup by elilo, the Kernel
must read it from these predefined areas in memory, into some of its
variables. I need to understand where this reading part happens in the
kernel. This is where I want to modify the resources, for future use
by the kernel !! I don't want to touch the elilo source, only the
kernel.
Hoping to hear from you soon.
Thanks and Regards,
Vaibhav.
On Wed, 2 Feb 2005 22:01:14 -0800, David Mosberger
<davidm@napali.hpl.hp.com> wrote:
> >>>>> On Thu, 3 Feb 2005 10:21:42 +0530, Vaibhav Sharma <vaibhav.sh@gmail.com> said:
>
> Vaibhav> Hi, I am investigating how linux initializes the memory in
> Vaibhav> IA64 machine. the flow, very broadly (i think) is:
> Vaibhav> **start_kernel-> setup_arch-> find_memory-> efi_memmap_walk
> Vaibhav> ** ( it does all all other things like unwind_init,
> Vaibhav> efi_init, etc, inbetween). The function efi_memmap_walk
> Vaibhav> uses the "IA64_boot_param" structure to read the memory
> Vaibhav> map. I wanted to know where and how this structure is
> Vaibhav> initialized, I mean how does it access the EFI table. Are
> Vaibhav> call-backs used to initialize this structure..??..Do these
> Vaibhav> call-backs use the API's to EFI table management...?
>
> The boot-param structure is setup by elilo.
>
> Look for a routine called sysdeps_create_boot_params() in the elilo sources.
>
> --david
>
next prev parent reply other threads:[~2005-02-03 7:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 4:52 IA64 memory Vaibhav Sharma
2005-02-03 6:01 ` David Mosberger
2005-02-03 7:15 ` Vaibhav Sharma [this message]
2005-02-04 2:31 ` David Mosberger
2005-02-06 6:21 ` Vaibhav Sharma
2005-02-08 18:17 ` David Mosberger
2005-02-20 11:30 ` Vaibhav Sharma
2005-02-20 15:57 ` Matthew Wilcox
2005-02-20 17:29 ` Bukie Mabayoje
2005-02-24 18:40 ` Bukie Mabayoje
2005-03-01 13:44 ` Vaibhav Sharma
2005-03-01 15:24 ` Alex Williamson
2005-03-01 15:32 ` Matthew Wilcox
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=851caabb0502022303709136b@mail.gmail.com \
--to=vaibhav.sh@gmail.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