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-devel

Re: [Xen-devel] where is writable page table implemented?

To: "Tim Deegan" <Tim.Deegan@xxxxxxxxxx>
Subject: Re: [Xen-devel] where is writable page table implemented?
From: weiming <zephyr.zhao@xxxxxxxxx>
Date: Tue, 1 Apr 2008 11:37:54 -0400
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 01 Apr 2008 08:38:24 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=c837dVZE1/RAsf9POlsAffzUS6af3SyvmufmbEzpnWg=; b=suC2CI+xOLj6vbugFg1jQQ2K4+/tRQBeOxCaQG7on+eouc0jl0+9vEHP1W8L5To4T8oM1ow+Kl38zYjtQV2Nmm2FY7pvRTucxi4iEt0HCUmmUvxHokl/odm2xhDR3RA9VBc7qgtE9QT7eYrV9zRoK6Q5Vf4nkQ8jgsSKNKaNBSQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=SaZUnK71bkoLpLthV95mGSke/F/QBdzX6N1CknzjA4yHkc9pFX8xn9/6rNSPFZEzx6FiqJkYD9hljxxWK+iBhzrzTn6d6+2BPp/WHBN4P1oiAsYW2RXQF5TAKYR3nUp6Clsod1ifGNrOIdywQdVLvaGCRE7U4gQQ+jKwNM/2y2w=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20080401083825.GA4628@xxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <add59a3f0803240918m1f882115h7c2ba64e2ca2139a@xxxxxxxxxxxxxx> <20080324162510.GD30315@xxxxxxxxxxxxxxxxxxxxx> <add59a3f0803241126i603eb40qfa1b57f917103e74@xxxxxxxxxxxxxx> <20080325104351.GA30991@xxxxxxxxxxxxxxxxxxxxx> <add59a3f0803301643r740ba4c5xda84c40b46d7a157@xxxxxxxxxxxxxx> <20080401083825.GA4628@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Tim,

Do you know under which situation we use writable page table instead of calling update_va_mapping?

And do you know the purpose of the counter defined in page_info.u.in_use.type_info?
I understand that xen needs to keep track of the type of each page (L1_page_table_page, L2_page_table_page, pinned, unpinned, validated, etc), but why do we need to use the lower 26 bits of "type_info" as a counter? (in "get_page_type()", the counter is increased. )  Similarly,  get_page() / put_page() also increases/decreases the page.count_info. Could you please give me some hint about the usage of such counters?

Thanks a lot!
Weiming


On Tue, Apr 1, 2008 at 4:38 AM, Tim Deegan <Tim.Deegan@xxxxxxxxxx> wrote:
At 19:43 -0400 on 30 Mar (1206906207), weiming wrote:
> with writable page table, why guest os still calls update_va_mapping to
> update the pte?

It's faster to call into Xen with an explicit modification, or a list of
them, than to have xen trap and do a full x86 instruction emaulation to
figure out what you werere doing.

Cheers,

Tim.

--
Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Principal Software Engineer, Citrix Systems (R&D) Ltd.
[Company #02300071, SL9 0DZ, UK.]

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>