All of lore.kernel.org
 help / color / mirror / Atom feed
From: PUCCETTI Armand <armand.puccetti@cea.fr>
To: xen-devel@lists.xensource.com
Subject: page tables location
Date: Wed, 21 Mar 2007 18:50:03 +0100	[thread overview]
Message-ID: <4601704B.4020805@cea.fr> (raw)

A few simple questions:

1. page tables: Could please someone lighten me up on where the page 
tables tree physically resides
on a 64 bits machine?  Are they contiguous and are they constrained some 
address space? which one?
Where (function) are these tables extended, when necessary?

2. alloc_bitmap: the variable alloc_bitmap that contains the flags to 
check if a page is allocated or not is initialised like this:

...
xenheap_phys_start = init_boot_allocator(_pa(&_end));
...

unsigned long init_boot_allocator(unsigned long bitmap_start)
{
  bitmap_start = round_pgup(bitmap_start);

  /* Allocate space for the allocation bitmap. */
  bitmap_size = max_page / 8;
  bitmap_size = round_pgup(bitmap_size);
  alloc_bitmap = (unsigned long *)phys_to_virt(bitmap_start);
  /* All allocated by default. */
  memset(alloc_bitmap, ~0, bitmap_size);
  return bitmap_start + bitmap_size;
}

so, alloc_bitmap is apparently put somewhere in virtual memory (a little 
after 0xFFFF830000100000
according to xen.lds.S). However, it seems that its 36K are physically 
allocated between 0x00000000004b0000  and 0x00000000004b9000. This is a 
reserved mem area, so how is alloc_bitmap placed at this
location?

3. Is there any physical memory map, explaining what objects are located 
in low mem at fixed addresses?
something that refines the one printed at boot time.

thanks
Armand

                 reply	other threads:[~2007-03-21 17:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4601704B.4020805@cea.fr \
    --to=armand.puccetti@cea.fr \
    --cc=xen-devel@lists.xensource.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.