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

[Xen-devel] Re: xentrace: broken by c/s 23050:4ebba54b666f

To: Christoph Egger <Christoph.Egger@xxxxxxx>
Subject: [Xen-devel] Re: xentrace: broken by c/s 23050:4ebba54b666f
From: Olaf Hering <olaf@xxxxxxxxx>
Date: Tue, 22 Mar 2011 15:25:33 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 22 Mar 2011 07:26:20 -0700
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1300803936; l=860; s=domk; d=aepfle.de; h=In-Reply-To:Content-Type:MIME-Version:References:Subject:Cc:To:From: Date:X-RZG-CLASS-ID:X-RZG-AUTH; bh=v0KHx5Rlw8/JLRalxtUn07b+yVg=; b=V/pcggCwdhh+/5zSasIe7OKv+KV+As2CqNJ/Ldk8JO2YDOODaZJ47+SWBwMiCNR/fPg 0VVBjj7uxP9y5IHsF7KX1LMlL/B0Id/hx1EerXqWAN/cLaSqzOsNhapQHJTs2ODGeCmoU XgNOks+FzwRb7QuYVHgg2hzJgUlESaGOT00=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110321212320.GA15820@xxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4D87841B.1000102@xxxxxxx> <20110321173859.GA21766@xxxxxxxxx> <20110321212320.GA15820@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
On Mon, Mar 21, Olaf Hering wrote:

> On Mon, Mar 21, Olaf Hering wrote:
> 
> > On Mon, Mar 21, Christoph Egger wrote:
> > 
> > > 
> > > Hi,
> > > 
> > > C/s 23050:4ebba54b666f broke xentrace:
> > > 
> > > # xentrace -e 0x8f000 ./xentrace.out
> > > (XEN) Xen trace buffers: cpu 0 p 0000000000000000
> > 
> > The system you test on has 8 cpus, like mine.
> > t_info_pages got too big, so alloc_xenheap_pages() failed.
> > Can you add a printk to se whats happening in calculate_tbuf_size()?
> 
> compile tested patch:

> +    gdprintk(XENLOG_INFO, "requested %u t_info_pages for %u trace pages on 
> %u cpus\n",
> +               t_info_pages, pages, num_online_cpus());

I can reproduce it now. For some reason the line above will print
nothing. A plain printk gives:

(XEN) requested 0 t_info_pages for 32 trace pages on 8 cpus

I will investigate.

Olaf

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel