From: Gerd Knorr <kraxel@bytesex.org>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Scott Parish <srparish@us.ibm.com>
Subject: Re: understanding __linear_l2_table and friends
Date: 20 Apr 2005 18:06:23 +0200 [thread overview]
Message-ID: <874qe1qvpc.fsf@bytesex.org> (raw)
In-Reply-To: <E1DOC4v-0002D8-00@mta1.cl.cam.ac.uk>
Keir Fraser <Keir.Fraser@cl.cam.ac.uk> writes:
> They aren't actually used during domain building,
Used anywhere else? Especially __linear_l2_table and
__linear_l3_table?
> Xen uses the common trick whereby each page directory maps
> itself. This means that every page-table entry is mapped into the
> address space at some virtual address.
Well, in PAE mode that trick doesn't fully work. It will do fine for
the l1 tables, I think also for l2, but certainly not for l3 due to
address space constrains ...
Gerd
--
#define printk(args...) fprintf(stderr, ## args)
next prev parent reply other threads:[~2005-04-20 16:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 23:03 understanding __linear_l2_table and friends Scott Parish
2005-04-20 10:05 ` Keir Fraser
2005-04-20 16:06 ` Gerd Knorr [this message]
2005-04-20 19:46 ` Scott Parish
-- strict thread matches above, loose matches on Subject: below --
2005-04-20 16:25 Ian Pratt
2005-04-20 16:31 ` Keir Fraser
2005-04-20 18:53 Ian Pratt
2005-04-20 19:14 ` Gerd Knorr
2005-04-20 20:27 Ian Pratt
2005-04-20 21:38 ` Gerd Knorr
2005-04-20 22:10 ` Ian Pratt
2005-04-21 13:51 Ian Pratt
2005-04-21 19:42 ` Gerd Knorr
2005-04-22 11:04 ` Andi Kleen
2005-04-22 20:47 ` Kip Macy
2005-04-23 15:08 ` Andi Kleen
2005-04-23 15:13 ` Wim Coekaerts
2005-04-23 15:28 ` Andi Kleen
2005-04-24 19:55 ` Gerd Knorr
2005-04-25 0:41 ` David Hopwood
2005-04-25 0:46 ` Mark Williamson
2005-04-25 2:53 ` David Hopwood
2005-04-21 21:13 Ian Pratt
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=874qe1qvpc.fsf@bytesex.org \
--to=kraxel@bytesex.org \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=srparish@us.ibm.com \
--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.