This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] MULTI_mmu_update, HYPERVISOR_mmu_update and pte entry

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] MULTI_mmu_update, HYPERVISOR_mmu_update and pte entry
From: Christopher Benninger <chrisbenninger@xxxxxxxxx>
Date: Thu, 19 May 2011 10:37:48 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Wei Liu <liuw@xxxxxxxxx>
Delivery-date: Thu, 19 May 2011 10:38:50 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=M++7M4OH8W69Yeubp8ZXE9JlMq3X5z2W2mP8Szezvxk=; b=BICgclbA1gyqdys7wCix5gy8pPxp5hT+3PjrilgpHipdnFN0XPaz75XdZdjNUuqjc6 9/dy8OKbAhkqXytSjs4XFGkGDzo2q6T2WqRlsyxEjM7LTZj8aKWxQsotiOBIEGr8/45K +VG201x/z2WDtBap4UFi1vMP/3cdIslOUrPx8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=nODIQXlh8LxXP5yPCU2l7d13Nmovv9HCk5oX+PmViNFMXy/MqRgGtNRSpDRnHHjKl1 zmPm0Jcc7ZlYfuByw1LDOuPILuV2flwTDBsRnYf+gPjJ3CGKFKvJojvf2+g9X+G7C+qJ Sb8UoYxfQcjUZsPIqcVEEGaV5QP6g1Guwbifk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1305706199.4198.0.camel@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <BANLkTim1p6W=zq9MDoU+xkmrR2xvapQ4mA@xxxxxxxxxxxxxx> <4DD2F6B1.5080208@xxxxxxxx> <BANLkTim4JrTUK5itYNqts4XPzTXma4Z=6A@xxxxxxxxxxxxxx> <BANLkTimQMJ4MceFvJ+yMxuCa7Tdt_qdtEA@xxxxxxxxxxxxxx> <1305706199.4198.0.camel@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

Are you talking about when DomU calls setpte? 

Chris Benninger

University of Victoria, Computer Science

On Wed, May 18, 2011 at 1:09 AM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> 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@xxxxxxxxx> 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.


Xen-devel mailing list