From: Andrew Theurer <habanero@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Xen development list <xen-devel@lists.xensource.com>,
Rolf Neugebauer <rn@acm.org>
Subject: Re: Why is 'emulate' as good as writable PT's?
Date: Mon, 05 Jun 2006 17:29:58 -0500 [thread overview]
Message-ID: <4484B066.1040201@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D4BA988@liverpoolst.ad.cl.cam.ac.uk>
Ian Pratt wrote:
>> Could there be situations were we are inadvertently triggering a
>> writable page table, where we should just be doing a
> update_va_mapping()?
>
> Almost certainly. Singleton (or small batch) updates should not be using
> writeable pagetables, and should use update_va_mapping (or mmu_update if
> the VA isn't known or may not be mapped).
>
> ~18 months ago Rolf wrote and checked in profile code to collect a
> histogram of the number of entries found to be modified when writeable
> pagetables are flushed.
> At the time there was a big spike at '1' which was fixed, but with all
> the various linux version upgrades it likely needs revisiting.
>
> The profile code also records the EIP that caused the writeable
> pagetables operation, so if you print out the value a few times you'll
> quickly find the culprit.
Thanks! It looks like the histogram and EIP logs in ptwr_flush are
still there, so we'll run again with perfc=y and see if we can pinpoint
the culprit.
-Andrew
next prev parent reply other threads:[~2006-06-05 22:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 22:17 Why is 'emulate' as good as writable PT's? Ian Pratt
2006-06-05 22:29 ` Andrew Theurer [this message]
2006-06-06 20:28 ` Andrew Theurer
2006-06-06 21:14 ` Keir Fraser
2006-06-06 22:02 ` Andrew Theurer
2006-06-08 16:05 ` Andrew Theurer
-- strict thread matches above, loose matches on Subject: below --
2006-06-12 9:15 Ian Pratt
2006-06-13 14:47 ` Andrew Theurer
2006-06-05 21:45 Andrew Theurer
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=4484B066.1040201@us.ibm.com \
--to=habanero@us.ibm.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=rn@acm.org \
--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.