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 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Xen at scale

To: "MAGENHEIMER,DAN (HP-FtCollins,ex1)" <dan.magenheimer@xxxxxx>
Subject: Re: [Xen-devel] Xen at scale
From: Alex Ho <alex.ho@xxxxxxxxxxxx>
Date: Tue, 23 Mar 2004 22:59:50 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 23 Mar 2004 23:00:16 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: <BAD2BC26CB905B469D66053BB354F83903E3C401@xxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Organization: Computer Laboratory, University of Cambridge
References: <BAD2BC26CB905B469D66053BB354F83903E3C401@xxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
can you call pdb-stub.c::breakpoint() early on during the domain startup
to force it into the debugger?   i'm planning to check in some code later
this week which will make debugging domains and processes a lot easier.

.a

On Tue, 23 Mar 2004 14:37:20 -0800
"MAGENHEIMER,DAN (HP-FtCollins,ex1)" <dan.magenheimer@xxxxxx> wrote:

> >> My wish list based on my experience so far:
> >>        HIGHMEM4G - This is my top wish, and I will work on it myself
> >>             when I get a chance, though I can't say when that
> >> will be.
> >
> >Agreed. It should just be a case of putting the CONFIG_HIGHMEM4G
> >stuff back into the following files:
> >
> >./include/asm-xeno/fixmap.h
> >./include/asm-xeno/highmem.h
> >./include/asm-xeno/pgtable.h
> >./include/asm-xeno/page.h
> >./arch/xeno/config.in
> >./arch/xeno/mm/init.c
> >./arch/xeno/kernel/setup.c
> 
> Here's a patch that adds back the CONFIG_HIGHMEM stuff.  It works
> fine with CONFIG_HIGHMEM off and with CONFIG_HIGHMEM on with
> dom0_memory <= 512MB, but fails with dom0_memory == 1GB (1048576)
> on my 2GB machine.
> 
> The failure condition is that DOM0 barely launches, then causes
> Xen to die and the machine reboots (even with reboot disabled, so
> it must be trashing something in Xen itself).  I haven't been able
> to get any debugging output (even panics) to show up from dom0 at all...
> perhaps this will be a good opportunity to try out Alex's pdb
> stuff.  (Alex, is there any way to set a breakpoint very early
> in xenolinux startup?)
> 
> Anyway, I thought I'd post it in case someone with more xenolinux
> setup/init debugging experience can easily spot/fix the problem,
> but I'll keep trying.  (Please email if you find/fix it, to put
> me out of my misery ;-)
> 
> As it works for everything that works today, the patch could be rolled
> into the mainline, possibly with a runtime check and nicer error
> message added.
> 
> Dan Magenheimer
> HP Labs Fort Collins
> 
> P.S. No changes appeared to be required in page.h or setup.c
> and I changed defconfig instead of config.in.
> 
> 


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>