From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Zachary Amsden <zach@vmware.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: how set_pte_at()'s vaddr and ptep args relate
Date: Tue, 07 Nov 2006 16:15:17 -0800 [thread overview]
Message-ID: <45512195.3060101@goop.org> (raw)
In-Reply-To: <45511DD4.80307@vmware.com>
Zachary Amsden wrote:
> "Who can discern his errors? Forgive my hidden faults."
In general that Book doesn't give much in the way of architectural
certainty. 3.12 IA32SDM isn't much better:
Whenever a page-directory or page-table entry is changed (including
when the present flag is set to zero), the operating-system must
immediately invalidate the corresponding entry in the TLB so that it
can be updated the next time the entry is referenced.
The parenthetic clause is annoyingly ambiguous: does it mean "when the
present flag is currently set to 0" or "when setting the present flag to
0"? The passive voice should always be avoided.
> Oh, wow. Unfortunately, the complexity isn't from how frequent or
> rare a kmapped PT access is, it is from it being there at all.
We'll see how it works out. What actually needs to do cross-process
pagetable manipulation? Fork? ptrace?
J
next prev parent reply other threads:[~2006-11-08 0:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 19:57 how set_pte_at()'s vaddr and ptep args relate Jeremy Fitzhardinge
2006-11-07 22:19 ` Zachary Amsden
2006-11-07 22:38 ` Jeremy Fitzhardinge
2006-11-07 23:33 ` Zachary Amsden
2006-11-07 23:42 ` Jeremy Fitzhardinge
2006-11-07 23:59 ` Zachary Amsden
2006-11-08 0:15 ` Jeremy Fitzhardinge [this message]
2006-11-08 0:19 ` Zachary Amsden
2006-11-08 8:34 ` Keir Fraser
2006-11-08 19:59 ` Jeremy Fitzhardinge
2006-11-08 20:18 ` Jeremy Fitzhardinge
2006-11-08 23:17 ` Keir Fraser
2006-11-08 23:25 ` Jeremy Fitzhardinge
2006-11-09 8:29 ` Keir Fraser
2006-11-09 9:15 ` Zachary Amsden
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=45512195.3060101@goop.org \
--to=jeremy@goop.org \
--cc=chrisw@sous-sol.org \
--cc=virtualization@lists.osdl.org \
--cc=zach@vmware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).