From: Gerd Knorr <kraxel@bytesex.org>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Ian Pratt <Ian.Pratt@cl.cam.ac.uk>,
ak@suse.de, Scott Parish <srparish@us.ibm.com>
Subject: Re: understanding __linear_l2_table and friends
Date: Thu, 21 Apr 2005 21:42:16 +0200 [thread overview]
Message-ID: <20050421194216.GB13678@bytesex> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3CC1@liverpoolst.ad.cl.cam.ac.uk>
> The alternative is to hack PAE Linux to force the L2 containing kernel
> mappings to be per-pagetable rather than shared. The downside of the is
> that we use an extra 4KB per pagetable, and have the hassle of faulting
> in kernel L2 mappings on demand (like non-PAE Linux has to). This plays
> nicely with the TLB flush filter, and is fine for SMP guests.
I think that one is better. The topmost L2 table with the kernel
mappings is a special case anyway because it also has the hypervisor
hole and thus differs from the other three L2 tables when it comes to
allocation and verification (and maybe other places as well).
I'm considering adding a new page type for the topmost L2 in PAE mode
to handle this. Comments? Better ideas?
Gerd
--
#define printk(args...) fprintf(stderr, ## args)
next prev parent reply other threads:[~2005-04-21 19:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 13:51 understanding __linear_l2_table and friends Ian Pratt
2005-04-21 19:42 ` Gerd Knorr [this message]
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-23 15:20 ` understanding __linear_l2_table and friends II Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2005-04-21 21:13 understanding __linear_l2_table and friends Ian Pratt
2005-04-20 20:27 Ian Pratt
2005-04-20 21:38 ` Gerd Knorr
2005-04-20 22:10 ` Ian Pratt
2005-04-20 18:53 Ian Pratt
2005-04-20 19:14 ` Gerd Knorr
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=20050421194216.GB13678@bytesex \
--to=kraxel@bytesex.org \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=ak@suse.de \
--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.