From: Kip Macy <kip.macy@gmail.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: recent changes to writable page tables on -unstable andxend
Date: Thu, 28 Apr 2005 17:16:40 -0700 [thread overview]
Message-ID: <b1fa2917050428171615981e64@mail.gmail.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3DE4@liverpoolst.ad.cl.cam.ac.uk>
> As I recall, we were taking the emulation path every time until quite
> recently. Are you sure you were actually using writeable pagetables
> before?
Well, last week I spent an hour or two removing places where FreeBSD
blew up when it tried to write directly to a page directory because
previously I didn't differentiate between PD and PT updates and today
when I removed the WRITABLE_PAGETABLES define the code initially
wouldn't compile. I can test out a tree from as of my checkin, but I'm
fairly positive.
> You probably want to augment the debug message to print out a bit more
> about the old and new pte, page type, and which pages are in wrpt mode.
Ok, I'll do that thanks.
-Kip
prev parent reply other threads:[~2005-04-29 0:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 23:56 recent changes to writable page tables on -unstable andxend Ian Pratt
2005-04-29 0:16 ` Kip Macy [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=b1fa2917050428171615981e64@mail.gmail.com \
--to=kip.macy@gmail.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--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.