From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xensource.com
Subject: Re: [PATCH] xentrace: dynamic tracebuffer size allocation
Date: Sat, 5 Feb 2011 17:32:39 +0100 [thread overview]
Message-ID: <20110205163239.GA26767@aepfle.de> (raw)
In-Reply-To: <20110205140717.GA3224@aepfle.de>
On Sat, Feb 05, Olaf Hering wrote:
>
> Allocate tracebuffers dynamically, based on the requested buffer size.
> Calculate t_info_size from requested t_buf size.
> Fix allocation failure path, free pages without the spinlock.
> The spinlock is not needed since tracing is not yet enabled.
> Remove casts for rawbuf, it can be a void pointer since no math is done.
>
> Signed-off-by: Olaf Hering <olaf@aepfle.de>
plus this change to fix a compile error after spinlock removal..
Index: xen-unstable.hg-4.1.22870/xen/common/trace.c
===================================================================
--- xen-unstable.hg-4.1.22870.orig/xen/common/trace.c
+++ xen-unstable.hg-4.1.22870/xen/common/trace.c
@@ -185,7 +185,6 @@ static int alloc_trace_bufs(unsigned int
*/
for_each_online_cpu(cpu)
{
- int flags;
void *rawbuf;
struct t_buf *buf;
@@ -243,7 +242,6 @@ static int alloc_trace_bufs(unsigned int
out_dealloc:
for_each_online_cpu(cpu)
{
- int flags;
void *rawbuf;
rawbuf = per_cpu(t_bufs, cpu);
next prev parent reply other threads:[~2011-02-05 16:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 14:07 [PATCH] xentrace: dynamic tracebuffer size allocation Olaf Hering
2011-02-05 16:32 ` Olaf Hering [this message]
2011-02-05 20:35 ` Keir Fraser
2011-02-06 13:39 ` Olaf Hering
2011-02-07 17:38 ` George Dunlap
2011-02-07 17:55 ` Olaf Hering
2011-03-14 17:33 ` Olaf Hering
2011-03-16 11:32 ` George Dunlap
2011-03-16 13:05 ` Olaf Hering
2011-03-16 14:18 ` George Dunlap
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=20110205163239.GA26767@aepfle.de \
--to=olaf@aepfle.de \
--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.