view xen/GUEST_CHANGES @ 922:fc5ae656dd1e

bitkeeper revision 1.582.1.2 (3fafc1a8WtDmHzijhEouIqSThPp1nA)

Fixes to xen_netwatch.
author kaf24@scramble.cl.cam.ac.uk
date Mon Nov 10 16:49:44 2003 +0000 (2003-11-10)
parents ac55fdc43f08
line source
2 The interface between Xen and overlying guest OSes has changed in the
3 following ways since version 1.0:
5 Modified hypercall 'pt_update'
6 ------------------------------
7 Page-table updates passed to the 'pt_update' hypercall must now
8 specify a virtual address that maps the PTE to be modified. Previously
9 a physical address was used, requiring Xen to temporarily map the PTE
10 into its own private region so that it could be read and written.
11 This affects only commands of type PGREQ_NORMAL_UPDATE and
14 New hypercall 'update_va_mapping'
15 ---------------------------------
16 A new high-speed page-table update method has been introduced, which
17 may be of particular benefit when fixing up application page faults.
18 Invoked as 'update_va_mapping(page_number, new_pte_value, flags)':
19 <page_number>: The virtual page number in the current address space
20 whose PTE is to be modified.
21 <new_pte_value>: The new value to write into the PTE.
22 <flags>: An ORed combination of
23 UVMF_INVLPG: Flush stale TLB entry of the updated page mapping
24 UVMF_FLUSH_TLB: Flush all TLB entries
25 You can see this new call in use in Xenolinux (common/memory.c).