All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Christoph Egger <Christoph.Egger@amd.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: xentrace: broken by c/s 23050:4ebba54b666f
Date: Mon, 21 Mar 2011 22:23:20 +0100	[thread overview]
Message-ID: <20110321212320.GA15820@aepfle.de> (raw)
In-Reply-To: <20110321173859.GA21766@aepfle.de>

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:


# HG changeset patch
# Parent c81f0ef5a77d90fbf108d3efe489d08df45b63c2
xentrace: print calculated numbers in calculate_tbuf_size()

Print number of pages to allocate for per-cpu tracebuffer and metadata
to ease debugging when allocation fails.

Signed-off-by: Olaf Hering <olaf@aepfle.de>

diff -r c81f0ef5a77d xen/common/trace.c
--- a/xen/common/trace.c	Mon Mar 21 14:52:27 2011 +0000
+++ b/xen/common/trace.c	Mon Mar 21 21:49:52 2011 +0100
@@ -127,6 +127,8 @@
     t_info_pages /= PAGE_SIZE;
     if ( t_info_pages % PAGE_SIZE )
         t_info_pages++;
+    gdprintk(XENLOG_INFO, "requested %u t_info_pages for %u trace pages on %u cpus\n",
+               t_info_pages, pages, num_online_cpus());
     return pages;
 }

  reply	other threads:[~2011-03-21 21:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21 17:00 xentrace: broken by c/s 23050:4ebba54b666f Christoph Egger
2011-03-21 17:38 ` Olaf Hering
2011-03-21 21:23   ` Olaf Hering [this message]
2011-03-22 14:25     ` Olaf Hering
2011-03-23  8:33 ` Olaf Hering

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=20110321212320.GA15820@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=Christoph.Egger@amd.com \
    --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.