xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: xen-devel@lists.xen.org
Cc: Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH 4 of 5] docs: Document HYPERVISOR_update_descriptor
Date: Fri, 02 Nov 2012 12:18:58 +0100	[thread overview]
Message-ID: <bb43f655bcc863d681fe.1351855138@hastur.hellion.org.uk> (raw)
In-Reply-To: <patchbomb.1351855134@hastur.hellion.org.uk>

# HG changeset patch
# User Ian Campbell <ian.campbell@citrix.com>
# Date 1351855019 -3600
# Node ID bb43f655bcc863d681fe30cea477f12333dd0cc6
# Parent  433d5d988e30e66a9c1f53a9b2c027692f9de11c
docs: Document HYPERVISOR_update_descriptor

Mark-up for inclusion of generated docs.

Signed-off-by: Ian Campbell <ian.campbell@citrix.com>

diff -r 433d5d988e30 -r bb43f655bcc8 xen/include/public/arch-x86/xen.h
--- a/xen/include/public/arch-x86/xen.h	Fri Nov 02 12:16:44 2012 +0100
+++ b/xen/include/public/arch-x86/xen.h	Fri Nov 02 12:16:59 2012 +0100
@@ -71,7 +71,7 @@ typedef unsigned long xen_pfn_t;
 #endif
 
 /*
- * SEGMENT DESCRIPTOR TABLES
+ * `incontents 200 segdesc Segment Descriptor Tables
  */
 /*
  * ` enum neg_errnoval
@@ -83,11 +83,24 @@ typedef unsigned long xen_pfn_t;
  * start of the GDT because some stupid OSes export hard-coded selector values
  * in their ABI. These hard-coded values are always near the start of the GDT,
  * so Xen places itself out of the way, at the far end of the GDT.
+ *
+ * NB The LDT is set using the MMUEXT_SET_LDT op of HYPERVISOR_mmuext_op
  */
 #define FIRST_RESERVED_GDT_PAGE  14
 #define FIRST_RESERVED_GDT_BYTE  (FIRST_RESERVED_GDT_PAGE * 4096)
 #define FIRST_RESERVED_GDT_ENTRY (FIRST_RESERVED_GDT_BYTE / 8)
 
+
+/*
+ * ` enum neg_errnoval
+ * ` HYPERVISOR_update_descriptor(u64 pa, u64 desc);
+ * `
+ * ` @pa   The machine physical address of the descriptor to
+ * `       update. Must be either a descriptor page or writable.
+ * ` @desc The descriptor value to update, in the same format as a
+ * `       native descriptor table entry.
+ */
+
 /* Maximum number of virtual CPUs in legacy multi-processor guests. */
 #define XEN_LEGACY_MAX_VCPUS 32

  parent reply	other threads:[~2012-11-02 11:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-02 11:18 [PATCH 0 of 5] docs: x86 PV MMU related functions Ian Campbell
2012-11-02 11:18 ` [PATCH 1 of 5] docs: document HYPERVISOR_update_va_mapping(_other_domain) Ian Campbell
2012-11-02 11:33   ` David Vrabel
2012-11-02 13:07     ` Ian Campbell
2012-11-19 11:31       ` Ian Jackson
2012-11-02 11:18 ` [PATCH 2 of 5] docs: Document HYPERVISOR_mmuext_op Ian Campbell
2012-11-19 11:31   ` Ian Jackson
2012-11-02 11:18 ` [PATCH 3 of 5] docs: Add ToC entry for start of day memory layout Ian Campbell
2012-11-19 11:32   ` Ian Jackson
2012-11-02 11:18 ` Ian Campbell [this message]
2012-11-19 11:31   ` [PATCH 4 of 5] docs: Document HYPERVISOR_update_descriptor Ian Jackson
2012-11-02 11:18 ` [PATCH 5 of 5] docs: Include prototype for HYPERVISOR_multicall Ian Campbell
2012-11-19 11:31   ` Ian Jackson
2012-11-12 10:04 ` [PATCH 0 of 5] docs: x86 PV MMU related functions Ian Campbell
2012-11-16 16:55 ` Ian Campbell
2012-11-18 21:02   ` Pasi Kärkkäinen
2012-11-19 10:29     ` Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bb43f655bcc863d681fe.1351855138@hastur.hellion.org.uk \
    --to=ian.campbell@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).