From: Flavio Leitner <fbl@conectiva.com.br>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: movl issue
Date: Thu, 30 Jun 2005 09:29:39 -0300 [thread overview]
Message-ID: <20050630122938.GA3560@conectiva.com.br> (raw)
Last one, now it is compiling.
----
Fixed to use 'mov' instead of 'movl' when dealing with segments.
Signed-off-by: Flavio B. Leitner <fbl@conectiva.com.br>
===== linux-2.6.11-xen-sparse/include/asm-xen/asm-i386/mmu_context.h 1.16 vs edited =====
--- 1.16/linux-2.6.11-xen-sparse/include/asm-xen/asm-i386/mmu_context.h 2005-06-01 12:37:20 -04:00
+++ edited/linux-2.6.11-xen-sparse/include/asm-xen/asm-i386/mmu_context.h 2005-06-29 18:03:08 -04:00
@@ -34,7 +34,7 @@
* are always kernel segments while inside the kernel. Must
* happen before reload of cr3/ldt (i.e., not in __switch_to).
*/
- __asm__ __volatile__ ( "movl %%fs,%0 ; movl %%gs,%1"
+ __asm__ __volatile__ ( "mov %%fs,%0 ; mov %%gs,%1"
: "=m" (*(int *)¤t->thread.fs),
"=m" (*(int *)¤t->thread.gs));
__asm__ __volatile__ ( "movl %0,%%fs ; movl %0,%%gs"
===== linux-2.6.11-xen-sparse/include/asm-xen/asm-i386/system.h 1.21 vs edited =====
--- 1.21/linux-2.6.11-xen-sparse/include/asm-xen/asm-i386/system.h 2005-06-16 07:43:56 -04:00
+++ edited/linux-2.6.11-xen-sparse/include/asm-xen/asm-i386/system.h 2005-06-29 17:37:46 -04:00
@@ -84,7 +84,7 @@
#define loadsegment(seg,value) \
asm volatile("\n" \
"1:\t" \
- "movl %0,%%" #seg "\n" \
+ "mov %0,%%" #seg "\n" \
"2:\n" \
".section .fixup,\"ax\"\n" \
"3:\t" \
@@ -102,7 +102,7 @@
* Save a segment register away
*/
#define savesegment(seg, value) \
- asm volatile("movl %%" #seg ",%0":"=m" (*(int *)&(value)))
+ asm volatile("mov %%" #seg ",%0":"=m" (*(int *)&(value)))
/*
* Clear and set 'TS' bit respectively
----
--
Flávio Bruno Leitner <fbl@conectiva.com.br>
[0EA2 7F40 4CF4 1E63 4AF6 33C0 3E10 E205 F251 EDDA]
next reply other threads:[~2005-06-30 12:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 12:29 Flavio Leitner [this message]
2005-06-30 13:33 ` movl issue Vincent Hanquez
2005-06-30 13:40 ` Flavio Leitner
2005-06-30 13:40 ` Rik Van Riel
2005-07-01 10:15 ` Vincent Hanquez
2005-07-01 21:12 ` Chris Wright
2005-07-03 11:10 ` Vincent Hanquez
2005-07-03 19:21 ` Chris Wright
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=20050630122938.GA3560@conectiva.com.br \
--to=fbl@conectiva.com.br \
--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.