public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Hildner <christian.hildner@hob.de>
To: linux-ia64@vger.kernel.org
Subject: Re: Page table mapped and identity segments!
Date: Tue, 04 Nov 2003 11:00:57 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106794372722594@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106794072219848@msgid-missing>

Ameya Mitragotri schrieb:

>Hello,
>I am refering to David's and Stephanes's book on the IA64 linux kernel.
From my understanding, 
>
>1) I can see that the PAGE_OFFSET which designates the start of
>the identity mapped segment starts at 0xe000000000000000 (region 7).
>
>2) This region has the linux kernel text/data/stack segments.
>
>Now after compiling the linux-2.6.0-test5 on an itanium-2 machine,
>the System.map generated contains addresses only starting with
>0xa0000..which means all these lie in the page table mapped segments
>(region 5).
>
>Why is this happening?
>
Kernel mapping has changed in the 2.6 kernel. The kernel is now 
relocatable (needed for new hardware). Because of that it was decided to 
move the kernel outside the identity mapped region. But the virtual to 
physical mappings are nevertheless done with the old mechanism of pinned 
large 64M pages for text and data. See head.S where these mappings are done.

Christian

> 
>
>Apologies if this is too trivial to be asked.
>
>Thanks
>Ameya
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>  
>



      parent reply	other threads:[~2003-11-04 11:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-04 10:22 Page table mapped and identity segments! Ameya Mitragotri
2003-11-04 10:29 ` Keith Owens
2003-11-04 11:00 ` Christian Hildner [this message]

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-106794372722594@msgid-missing \
    --to=christian.hildner@hob.de \
    --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