From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kip Macy Subject: Re: getting debug output from Xen during domain creation Date: Sun, 22 Feb 2004 08:26:42 -0800 (PST) Sender: xen-devel-admin@lists.sourceforge.net Message-ID: <20040222082020.C84871@demos.bsdclusters.com> References: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: In-Reply-To: Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Keir Fraser Cc: Ian Pratt , xen-devel@lists.sourceforge.net List-Id: xen-devel@lists.xenproject.org I think I'm doing something wrong with my configuration. The only place where I can get any DOM0 output from is xen_dmesg.py. There I actually see a line that I stuck into do_mmu_update as a test of the debug code itself: DOM0: (file=memory.c, line=916) do_mmu_update called DOM0: (file=memory.c, line=916) do_mmu_update called DOM0: (file=memory.c, line=916) do_mmu_update called DOM0: (file=memory.c, line=916) do_mmu_update called Minor pet peeve: "shutdown -r now", doesn't actually cause a reboot. Every time I want to change xen, I have to go downstairs to the machine and power-cycle it by hand. -Kip On Sun, 22 Feb 2004, Keir Fraser wrote: > > Looks like I may have foxed you --- I modified the MEM_LOG definition > this morning in response to your earlier email. Before that it wasn't > gated on NDEBUG. So if you run your debug build now then you should > get useful output. > > -- Keir > > > > Well ... > > > > 1) MEM_LOG is gated by NDEBUG: > > #ifndef NDEBUG > > #define MEM_LOG(_f, _a...) \ > > printk("DOM%llu: (file=memory.c, line=%d) " _f "\n", \ > > current->domain, __LINE__, ## _a ) > > > > #else > > #define MEM_LOG(_f, _a...) ((void)0) > > #endif > > > > 2) I've checked the C preprocessor output - and the printf statements > > are being generated. > > > > 3) Just for grins I've checked the output of strings on the object file > > to make sure that the strings were in fact there. > > > > > > I think something else is going on. > > > > > > -Kip > > > > > > On Sun, 22 Feb 2004, Ian Pratt wrote: > > > > > > > > > I've removed the DNDEBUG from xen/arch/i386/Rules.mk. However, during > > > > a failed mmu_update I'm not seeing anything in /var/log/messages or any > > > > output from xen_read_console. > > > > > > Try enabling MEM_LOG in xen/common/memory.c [*] > > > > > > This should probably be the default for DEBUG builds. > > > > > > Ian > > > > > > [*] Last time I looked, the macro was missing a '\' which you'll > > > need. > > > > > > > > > ------------------------------------------------------- > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > Build and deploy apps & Web services for Linux with > > > a free DVD software kit from IBM. Click Now! > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > _______________________________________________ > > > Xen-devel mailing list > > > Xen-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/xen-devel > > > > > > > > > ------------------------------------------------------- > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > Build and deploy apps & Web services for Linux with > > a free DVD software kit from IBM. Click Now! > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/xen-devel > > ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click