xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: xen-devel@lists.xen.org
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: [PATCH 7/8] docs: Document start_info changes in Xen 4.2.
Date: Mon, 28 Jan 2013 13:32:09 -0500	[thread overview]
Message-ID: <1359397930-9311-8-git-send-email-konrad.wilk@oracle.com> (raw)
In-Reply-To: <1359397930-9311-1-git-send-email-konrad.wilk@oracle.com>

The git commit 7a9d7646307b7c872b8dbd7546579acd3b54223d "x86/32-on-64:
adjust Dom0 initial page table layout" fixes a bug in the reported
value of pt_base versus what is stored in the %cr3 register. This
documents this in the start of the world header note.

Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
---
 xen/include/public/xen.h | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/xen/include/public/xen.h b/xen/include/public/xen.h
index c50bbfc..1685317 100644
--- a/xen/include/public/xen.h
+++ b/xen/include/public/xen.h
@@ -705,6 +705,13 @@ typedef struct shared_info shared_info_t;
  *  8. There is guaranteed to be at least 512kB padding after the final
  *     bootstrap element. If necessary, the bootstrap virtual region is
  *     extended by an extra 4MB to ensure this.
+ *
+ * Note: Prior to 7a9d7646307b7c872b8dbd7546579acd3b54223d ("x86/32-on-64:
+ * adjust Dom0 initial page table layout") the 3.e) contained two different
+ * values with a 64-bit hypervisor and a 32-bit initial domain kernel. The
+ * pt_base pointed to the L4 (setup by the hypervisor and not used by
+ * the guest) and the %cr3 pointed to the L3. This meant an difference of
+ * one page.
  */
 
 #define MAX_GUEST_CMDLINE 1024
-- 
1.7.11.7

  parent reply	other threads:[~2013-01-28 18:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28 18:32 [DOCS/PATCH] http://wiki.xen.org/wiki/X86_Paravirtualised_Memory_Management changes Konrad Rzeszutek Wilk
2013-01-28 18:32 ` [PATCH 1/8] docs: Document the ELF notes Konrad Rzeszutek Wilk
2013-01-29  9:16   ` Ian Campbell
2013-01-28 18:32 ` [PATCH 2/8] docs: Provide some examples of the various ELF values Konrad Rzeszutek Wilk
2013-01-29  9:23   ` Ian Campbell
2013-01-28 18:32 ` [PATCH 3/8] docs: Document the ELF_FEATURES entry Konrad Rzeszutek Wilk
2013-01-29  9:23   ` Ian Campbell
2013-01-28 18:32 ` [PATCH 4/8] docs: Add some extra details to the ELF note Konrad Rzeszutek Wilk
2013-01-29  9:26   ` Ian Campbell
2013-01-28 18:32 ` [PATCH 5/8] docs: Document the shared structure Konrad Rzeszutek Wilk
2013-01-29  9:26   ` Ian Campbell
2013-01-28 18:32 ` [PATCH 6/8] docs: Document the dom0_vga_console_info structure Konrad Rzeszutek Wilk
2013-01-29  9:31   ` Ian Campbell
2013-01-30 17:10     ` Konrad Rzeszutek Wilk
2013-01-28 18:32 ` Konrad Rzeszutek Wilk [this message]
2013-01-29  9:37   ` [PATCH 7/8] docs: Document start_info changes in Xen 4.2 Ian Campbell
2013-01-30 17:23     ` Konrad Rzeszutek Wilk
2013-01-31  9:58       ` Ian Campbell
2013-01-28 18:32 ` [PATCH 8/8] docs: Document the XenBus structure Konrad Rzeszutek Wilk
2013-01-29  9:38   ` Ian Campbell
2013-01-29 10:05 ` [DOCS/PATCH] http://wiki.xen.org/wiki/X86_Paravirtualised_Memory_Management changes 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=1359397930-9311-8-git-send-email-konrad.wilk@oracle.com \
    --to=konrad@kernel.org \
    --cc=konrad.wilk@oracle.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).