From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Satya <satyakiran@gmail.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Xeno Linux never pins L1 tables ?
Date: Tue, 16 Oct 2007 14:18:00 -0700 [thread overview]
Message-ID: <47152A88.4080401@goop.org> (raw)
In-Reply-To: <acbcf3840710161359x40cd6d08xe6178c4438500efd@mail.gmail.com>
Satya wrote:
> Wonder what happens if an L1 page is created *after* a PGD is pinned ?
> I think I have to explicitly pin the L1 page then? or unlikely( does
> Xen pin it when I map into into the pinned PGD using a hypercall )
When you update the L2 entry to point to the L1, Xen checks to make sure
the L1 page is all OK (read-only, valid contents), then pins it to the
rest of the pagetable.
J
prev parent reply other threads:[~2007-10-16 21:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 14:44 Xeno Linux never pins L1 tables ? Satya
2007-10-16 14:47 ` Keir Fraser
2007-10-16 15:29 ` Mark Williamson
2007-10-16 15:48 ` Satya
2007-10-16 16:10 ` Mark Williamson
2007-10-16 20:55 ` Satya
2007-10-16 19:57 ` Jeremy Fitzhardinge
2007-10-16 20:59 ` Satya
2007-10-16 21:18 ` Jeremy Fitzhardinge [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=47152A88.4080401@goop.org \
--to=jeremy@goop.org \
--cc=satyakiran@gmail.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.