WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Xen

xen-devel

[Top] [All Lists]

[Xen-devel] calling printk early enough kills dom0 boot on x86-64

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] calling printk early enough kills dom0 boot on x86-64
From: Muli Ben-Yehuda <muli@xxxxxxxxxx>
Date: Wed, 7 Jun 2006 18:22:02 +0300
Cc: Muli Ben-Yehuda <muli@xxxxxxxxxx>, Jon Mason <jdmason@xxxxxxxxxx>
Delivery-date: 2006年6月07日 08:22:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.11
If I apply the following patch and boot with it on x86-64, dom0 boot
hangs in random places. I found it while adding full ioremap
support. I suspect an overflow in the console subsystem due to ioremap
being called before the console is fuly set up, but did not have time
to fully investigate yet. If anyone wants to take a stab at fixing
this, please do :-)
Cheers,
Muli
diff -r c191c649cdb3 xen/include/asm-x86/io.h
--- a/xen/include/asm-x86/io.h Tue Jun 06 10:25:59 2006 +0100
+++ b/xen/include/asm-x86/io.h Wed Jun 07 18:03:13 2006 +0300
@@ -6,7 +6,14 @@
 #include <asm/page.h>
 
 /* We don't need real ioremap() on Xen/x86. */
-#define ioremap(x,l) (__va(x))
+static inline void* ioremap(unsigned long x, unsigned long l)
+{
+ printk("ieeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee!\n");
+ printk("ieeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee!\n");
+ printk("ieeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee!\n");
+ printk("ieeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee!\n");
+ return __va(x);
+}
 
 #define readb(x) (*(volatile char *)(x))
 #define readw(x) (*(volatile short *)(x))
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] calling printk early enough kills dom0 boot on x86-64, Muli Ben-Yehuda <=
Previous by Date: [Xen-devel] Debugging user-space applications with gdbserver-xen? , Simon Kagstrom
Next by Date: [Xen-devel] Re: [Xen-changelog] [xen-unstable] Expose the exception thrown by xen.lowlevel.xs. , Hollis Blanchard
Previous by Thread: [Xen-devel] Debugging user-space applications with gdbserver-xen? , Simon Kagstrom
Next by Thread: [Xen-devel] Re: [Xen-changelog] [xen-unstable] Expose the exception thrown by xen.lowlevel.xs. , Hollis Blanchard
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /