From: Scott Parish <srparish@us.ibm.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: Xen Development List <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Fixing stack alignment in x86-64 Xen
Date: Wed, 18 May 2005 05:07:21 +0000 [thread overview]
Message-ID: <20050518050720.GI27910@us.ibm.com> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D3720017304021C2C@scsmsx402.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 503 bytes --]
On Tue, May 17, 2005 at 07:25:46PM -0700, Nakajima, Jun wrote:
> Long mode needs to align the stack on a 16-byte boundary. Recent changes
> to Xen broke the requirement, and x86-64 XenLinux stopped booting. The
> attached fixes the problem.
Awesome!
I also needed the attached patch, which between the two of these,
makes one wonder how stuff like this is ending up in the tree. Is
code getting checked in without even being compile tested?
sRp
--
Scott Parish
Signed-off-by: srparish@us.ibm.com
[-- Attachment #2: rex.diff --]
[-- Type: text/plain, Size: 948 bytes --]
diff -rN -u -p old-xen-64/xen/arch/x86/x86_64/entry.S new-xen-64/xen/arch/x86/x86_64/entry.S
--- old-xen-64/xen/arch/x86/x86_64/entry.S 2005-05-17 19:23:04.000000000 +0000
+++ new-xen-64/xen/arch/x86/x86_64/entry.S 2005-05-18 00:44:21.000000000 +0000
@@ -314,10 +314,10 @@ FLT4: movq %rax,16(%rsi)
movq EDOMAIN_vcpu_info(%rbx),%rax
pushq VCPUINFO_upcall_mask(%rax)
testb $TBF_INTERRUPT,%cl
- setnz VCPUINFO_upcall_mask(%eax)# TBF_INTERRUPT -> clear upcall mask
+ setnz VCPUINFO_upcall_mask(%rax)# TBF_INTERRUPT -> clear upcall mask
popq %rax
shll $16,%eax # Bits 16-23: saved_upcall_mask
- movw UREGS_cs+8(%esp),%ax # Bits 0-15: CS
+ movw UREGS_cs+8(%rsp),%ax # Bits 0-15: CS
FLT5: movq %rax,8(%rsi) # CS/saved_upcall_mask
movq UREGS_rip+8(%rsp),%rax
FLT6: movq %rax,(%rsi) # RIP
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2005-05-18 5:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 2:25 [PATCH] Fixing stack alignment in x86-64 Xen Nakajima, Jun
2005-05-18 5:07 ` Scott Parish [this message]
2005-05-18 7:35 ` Keir Fraser
2005-05-18 14:06 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2005-05-18 7:36 Ian Pratt
2005-05-18 15:09 Nakajima, Jun
2005-05-18 15:32 ` Andi Kleen
2005-05-18 15:57 Nakajima, Jun
2005-05-18 16:14 ` Andi Kleen
2005-05-18 16:38 Nakajima, Jun
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=20050518050720.GI27910@us.ibm.com \
--to=srparish@us.ibm.com \
--cc=jun.nakajima@intel.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.