All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Gorm Hansen <jacobg@diku.dk>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Tracking changes to writable page tables
Date: Sun, 15 May 2005 12:23:08 -0700	[thread overview]
Message-ID: <4287A19C.8070702@diku.dk> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E401D@liverpoolst.ad.cl.cam.ac.uk>

Ian Pratt wrote:
>>It looks like xenlinux 2.6 now uses writable page tables by 
>>default (I can't find the switch to enable/disable them).
>>
>>I need to track writes to page tables, and I was wondering if 
>>it is possible to get a page fault upon writes to read-only 
>>mapped page tables, as when writing to other read-only mappings?
> 
> 
> Hmm, I can see that the current model makes like difficult for you
> (though self-migration is a pretty twisted thing to be trying to do
> anyway :-)
> 
> I wander if we should steal one of the OS bits in the PTE to
> differentiate writable pagetable mappings? You could then take a normal
> RO fault, set the bit, and then retry to have Xen do pagetable the work.
> 
> This would arguably be cleaner, though we've been reluctant to steal OS
> bits just incase there's some OS out there that uses them all.

Actually, it seems this could be done without using an AVL bit, as this
is really per-frame rather than per-VA information. If the pte-pin call
could add a 'propagate page fault' flag to the PTE frame, then I could
still get the first fault to the guest, and then remove the pinning bit
to prevent the rest of the faults.

Jacob

  parent reply	other threads:[~2005-05-15 19:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-15  4:57 Tracking changes to writable page tables Ian Pratt
2005-05-15  7:08 ` Jacob Gorm Hansen
2005-05-15  7:26   ` Jacob Gorm Hansen
2005-05-15  8:30 ` Jacob Gorm Hansen
2005-05-15 19:23 ` Jacob Gorm Hansen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-15 10:00 Ian Pratt
2005-05-15  9:50 Ian Pratt
2005-05-15  2:17 Jacob Gorm Hansen

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=4287A19C.8070702@diku.dk \
    --to=jacobg@diku.dk \
    --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.