From: Gerd Knorr <kraxel@bytesex.org>
To: Ian Pratt <m+Ian.Pratt@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: Wed, 20 Apr 2005 21:14:46 +0200 [thread overview]
Message-ID: <20050420191445.GA1262@bytesex> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3C82@liverpoolst.ad.cl.cam.ac.uk>
On Wed, Apr 20, 2005 at 07:53:00PM +0100, Ian Pratt wrote:
> > Gerd is correct that it does not fully work for PAE, but not
> > simply because of address-space considerations.
Well, sort of. The trick requires that the linear page table address
space is aligned to what the topmost page table level can handle. And
it eats one entry. We would have to align the linear page table @ 3GB
and waste 1GB address space, then the self-referencing trick would work
even with the 3rd level I think. Obviously not an option ;)
> We have to take 4 slots in the L2 handling the top of the VA space, and
> have the four slots point at the 4 L2s. We can use this to access all
> the L1's and L2's.
That's exactly what I'm doing at the moment.
> We then take another slot in the uppermost L2 and have it point at the
> L3.
That I don't ;)
While I'm at it: Which levels writable pagetables are used for
(without shadowing)? Only the first? Or also the other ones?
Gerd
--
#define printk(args...) fprintf(stderr, ## args)
next prev parent reply other threads:[~2005-04-20 19:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 18:53 understanding __linear_l2_table and friends Ian Pratt
2005-04-20 19:14 ` Gerd Knorr [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-21 21:13 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-20 20:27 Ian Pratt
2005-04-20 21:38 ` Gerd Knorr
2005-04-20 22:10 ` Ian Pratt
2005-04-20 16:25 Ian Pratt
2005-04-20 16:31 ` Keir Fraser
2005-04-19 23:03 Scott Parish
2005-04-20 10:05 ` Keir Fraser
2005-04-20 16:06 ` Gerd Knorr
2005-04-20 19:46 ` Scott Parish
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=20050420191445.GA1262@bytesex \
--to=kraxel@bytesex.org \
--cc=m+Ian.Pratt@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.