WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

Re: [Xen-ia64-devel] Modify to introduce delayed p2m table destruction

To: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Subject: Re: [Xen-ia64-devel] Modify to introduce delayed p2m table destruction
From: Doi.Tsunehisa@xxxxxxxxxxxxxx
Date: Mon, 06 Nov 2006 15:15:22 +0900
Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 05 Nov 2006 22:15:49 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: Your message of Mon, 06 Nov 2006 12:48:35 +0900. <20061106034835.GA2868%yamahata@xxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20061102103405.GA17534%yamahata@xxxxxxxxxxxxx> <200611060324.kA63OOF18926@xxxxxxxxxxxxxxxxxxxxxxxxxxx><20061106034835.GA2868%yamahata@xxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
You (yamahata) said:
>>   Hmm, I've thought that gnttab_release_mapping() ensures it...
> 
> No. gnttab_release_mapping() is for a domain which maps a page granted by
> another domain. Not for a domain which grants page mapping.

  Ok. I understood it.

>>> However during shadow_teardown_xxx() in your patch
>>> other domain might access the p2m table and struct page_info.
>>> Page reference convension must be kept right during them.
>> 
>>   Yes, it might access them. In past, I thought so, but after
>> discussion about delayed p2m table destruction of shadow2, I've be
>> satisfied that get_page avoids memory corruption finally.
> 
> You might understand x86 shadow code.
> However you must understand IA64 code too.
> It would be effective to understand IA64 code by analogy of
> x86 shadow code, But they're different.

  Hmm, I don't understand the difference.

  Can you give me suggestion about the difference ?

Thanks,
- Tsunehisa Doi

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

<Prev in Thread] Current Thread [Next in Thread>