[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Incorrect update_va_mapping call in interface.tex (Interface Manual).

  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Bruce Montague" <Bruce_Montague@xxxxxxxxxxxx>
  • Date: Fri, 30 Nov 2007 14:34:21 -0700
  • Delivery-date: Fri, 30 Nov 2007 13:36:44 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcgzmMVI58rE4Y6eQo+2fAotrvVXxw==
  • Thread-topic: Incorrect update_va_mapping call in interface.tex (Interface Manual).

At the bottom of page 40 of the Interface manual, an "update_va_mapping"
prototype is shown, but it should be an "update_va_mapping_otherdomain"
prototype. (This prototype introduces the "update_va_mapping_otherdomain"
hypercall documentation, so the association between hypercall and documentation
is wrong.) Patch below.
- bruce
diff -r e10eacec8b91 docs/src/interface.tex
--- a/docs/src/interface.tex    Wed Nov 28 22:36:33 2007 +0000
+++ b/docs/src/interface.tex    Fri Nov 30 11:15:45 2007 -0800
@@ -1831,7 +1831,7 @@ the pages of others:
 the pages of others:
-\hypercall{update\_va\_mapping(unsigned long va, uint64\_t val,
+\hypercall{update\_va\_mapping\_otherdomain(unsigned long va, uint64\_t val,
                          unsigned long flags, domid\_t domid)}
 Identical to {\bf update\_va\_mapping} save that the pages being


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.