From: Olaf Hering <olaf@aepfle.de>
To: George Dunlap <dunlapg@umich.edu>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: how to avoid lost trace records?
Date: Thu, 25 Nov 2010 22:04:08 +0100 [thread overview]
Message-ID: <20101125210408.GA16766@aepfle.de> (raw)
In-Reply-To: <AANLkTinprmdxM3EWN_59hEVc5fp0xNdh2XmDwUypimLR@mail.gmail.com>
[ Sorry, this mutt process was suspended and I didnt notice ... ]
On Mon, Nov 22, George Dunlap wrote:
> Olaf,
>
> Dang, 8 megs per cpu -- but I guess that's really not so much overhead
> on a big machine; and it's definitely worth getting around the lost
> records issue. Send the T_INFO_PAGES patch to the list, and see what
> Keir thinks.
The change is as simple as this, for xen-unstable. 4.0 needs to add the
get_order_from_pages() for alloc_xenheap_pages() calls.
A dynamic trace buffer allocation, and also allowing dynamic mask as
cmdline option, should be added. I have added this line to trace.c to
allow an event mask during booting:
integer_param("tbuf_event_mask", tb_event_mask);
Olaf
---
xen/common/trace.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- xen-unstable.hg-4.1.22415.orig/xen/common/trace.c
+++ xen-unstable.hg-4.1.22415/xen/common/trace.c
@@ -48,7 +48,8 @@ integer_param("tbuf_size", opt_tbuf_size
/* Pointers to the meta-data objects for all system trace buffers */
static struct t_info *t_info;
-#define T_INFO_PAGES 2 /* Size fixed at 2 pages for now. */
+#define T_INFO_PAGES_ORDER 1 /* Size fixed at 2 pages for now. */
+#define T_INFO_PAGES (1 << T_INFO_PAGES_ORDER)
#define T_INFO_SIZE ((T_INFO_PAGES)*(PAGE_SIZE))
static DEFINE_PER_CPU_READ_MOSTLY(struct t_buf *, t_bufs);
static DEFINE_PER_CPU_READ_MOSTLY(unsigned char *, t_data);
next prev parent reply other threads:[~2010-11-25 21:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 15:46 how to avoid lost trace records? Olaf Hering
2010-11-19 21:30 ` Olaf Hering
2010-11-20 20:21 ` Olaf Hering
2010-11-22 11:53 ` George Dunlap
2010-11-22 12:40 ` Olaf Hering
2010-11-22 12:51 ` George Dunlap
2010-11-22 13:46 ` Keir Fraser
2010-11-22 14:43 ` George Dunlap
2010-11-25 21:04 ` Olaf Hering [this message]
2010-11-25 22:27 ` Keir Fraser
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=20101125210408.GA16766@aepfle.de \
--to=olaf@aepfle.de \
--cc=dunlapg@umich.edu \
--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.