xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: chrisbenninger <chrisbenninger@gmail.com>
To: xen-devel@lists.xensource.com
Subject: MULTI_mmu_update, HYPERVISOR_mmu_update and pte entry
Date: Thu, 12 May 2011 15:41:43 -0700	[thread overview]
Message-ID: <BANLkTim1p6W=zq9MDoU+xkmrR2xvapQ4mA@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 684 bytes --]

Hi, I am working on being able to determine which process owns a PTE being
changed during each MMU update in 64-bit paravirtualized mode. I have a
couple questions here.

1. When a linux DomU wants to make an update to a PTE, it calls
HYPERVISOR_mmu_update? In my case it appears to be calling MULTI_mmu_update
mostly. Are these two functions the only primary ways a VM will ask for an
MMU update?

2. The mmu_update struct that comes along with a MMU update has a *unint64_t
ptr*  which is a machine address to the PTE being changed. Is there any way
to use this machine address and determine the pte_t or page from within a
DomU?

Thanks for any help you can give!

Chris Benninger

[-- Attachment #1.2: Type: text/html, Size: 870 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

             reply	other threads:[~2011-05-12 22:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12 22:41 chrisbenninger [this message]
2011-05-17 22:29 ` MULTI_mmu_update, HYPERVISOR_mmu_update and pte entry Jeremy Fitzhardinge
2011-05-18  5:25   ` Christopher Benninger
2011-05-18  5:47     ` Wei Liu
2011-05-18  8:09       ` Jeremy Fitzhardinge
2011-05-19 17:37         ` Christopher Benninger
2011-05-19 17:49           ` Jeremy Fitzhardinge

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='BANLkTim1p6W=zq9MDoU+xkmrR2xvapQ4mA@mail.gmail.com' \
    --to=chrisbenninger@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 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).