From: Christopher Benninger <chrisbenninger@gmail.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen-devel@lists.xensource.com, Wei Liu <liuw@liuw.name>
Subject: Re: MULTI_mmu_update, HYPERVISOR_mmu_update and pte entry
Date: Thu, 19 May 2011 10:37:48 -0700 [thread overview]
Message-ID: <BANLkTikc6uumHUicraZp4TH51=Jz7_Ry2g@mail.gmail.com> (raw)
In-Reply-To: <1305706199.4198.0.camel@abulafia.goop.org>
[-- Attachment #1.1: Type: text/plain, Size: 1026 bytes --]
Interesting,
Are you talking about when DomU calls setpte?
Chris Benninger
University of Victoria, Computer Science
cbenning@cs.uvic.ca
http://benninger.ca
On Wed, May 18, 2011 at 1:09 AM, Jeremy Fitzhardinge <jeremy@goop.org>wrote:
> On Wed, 2011-05-18 at 13:47 +0800, Wei Liu wrote:
> > On Wed, May 18, 2011 at 1:25 PM, Christopher Benninger
> > <chrisbenninger@gmail.com> wrote:
> > > Hi Jeremy,
> > > I am definitely doing something weird, but on purpose. I am trying to
> > > determine which process specifically owns the pte in question. I have a
> domU
> > > module which I can ask for information, I just dont know how to get the
> ptr
> > > provided, into a useful context I can send it.
> >
> > Most pte updates belong to current process. Maybe you can use CR3 to
> > determine to which page table a specified pte belongs. But it may be
> > hard to determine the actual task_struct IMHO.
>
> If you can record it at the time of the setpte, its easy: "current" is
> always the current task.
>
> J
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 1718 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-05-19 17:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 22:41 MULTI_mmu_update, HYPERVISOR_mmu_update and pte entry chrisbenninger
2011-05-17 22:29 ` 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 [this message]
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='BANLkTikc6uumHUicraZp4TH51=Jz7_Ry2g@mail.gmail.com' \
--to=chrisbenninger@gmail.com \
--cc=jeremy@goop.org \
--cc=liuw@liuw.name \
--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).