From: George Dunlap <george.dunlap@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 1 of 3] xentrace: correct formula to calculate t_info_pages
Date: Fri, 01 Apr 2011 11:32:19 +0100 [thread overview]
Message-ID: <1301653939.9447.11.camel@elijah> (raw)
In-Reply-To: <8a2ce5e49b2c5f2e0137.1301508273@localhost>
Acked-by: George Dunlap <george.dunlap@eu.citrix.com>
On Wed, 2011-03-30 at 19:04 +0100, Olaf Hering wrote:
> # HG changeset patch
> # User Olaf Hering <olaf@aepfle.de>
> # Date 1301423840 -7200
> # Node ID 8a2ce5e49b2c5f2e013734b5d53eae37572f4101
> # Parent 45eeeb6d0481efaab2a59941e1b8e061aead37d4
> xentrace: correct formula to calculate t_info_pages
>
> The current formula to calculate t_info_pages, based on the initial
> code, is slightly incorrect. It may allocate more than needed.
> Each cpu has some pages/mfns stored as uint32_t.
> That list is stored with an offset at tinfo.
>
> Signed-off-by: Olaf Hering <olaf@aepfle.de>
>
> ---
> xen/common/trace.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff -r 45eeeb6d0481 -r 8a2ce5e49b2c xen/common/trace.c
> --- a/xen/common/trace.c Tue Mar 29 16:34:01 2011 +0100
> +++ b/xen/common/trace.c Tue Mar 29 20:37:20 2011 +0200
> @@ -110,7 +110,7 @@
> {
> struct t_buf dummy;
> typeof(dummy.prod) size;
> - unsigned int t_info_words, t_info_bytes;
> + unsigned int t_info_words;
>
> /* force maximum value for an unsigned type */
> size = -1;
> @@ -125,9 +125,8 @@
> pages = size;
> }
>
> - t_info_words = num_online_cpus() * pages + t_info_first_offset;
> - t_info_bytes = t_info_words * sizeof(uint32_t);
> - t_info_pages = PFN_UP(t_info_bytes);
> + t_info_words = num_online_cpus() * pages * sizeof(uint32_t);
> + t_info_pages = PFN_UP(t_info_first_offset + t_info_words);
> printk(XENLOG_INFO "xentrace: requesting %u t_info pages "
> "for %u trace pages on %u cpus\n",
> t_info_pages, pages, num_online_cpus());
next prev parent reply other threads:[~2011-04-01 10:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 18:04 [PATCH 0 of 3] xentrace updates Olaf Hering
2011-03-30 18:04 ` [PATCH 1 of 3] xentrace: correct formula to calculate t_info_pages Olaf Hering
2011-04-01 10:32 ` George Dunlap [this message]
2011-03-30 18:04 ` [PATCH 2 of 3] xentrace: use tbuf_size for overflow check Olaf Hering
2011-04-01 11:18 ` George Dunlap
2011-04-05 10:19 ` Olaf Hering
2011-04-07 13:50 ` Olaf Hering
2011-04-18 18:45 ` non-contiguous allocations Olaf Hering
2011-04-26 11:51 ` Jan Beulich
2011-05-06 10:25 ` Olaf Hering
2011-05-06 10:45 ` Jan Beulich
2011-05-06 18:12 ` Olaf Hering
2011-05-06 18:46 ` Keir Fraser
2011-05-07 8:39 ` Olaf Hering
2011-05-07 16:31 ` Keir Fraser
2011-05-09 8:30 ` Jan Beulich
2011-05-09 8:34 ` Keir Fraser
2011-05-09 12:43 ` Olaf Hering
2011-05-09 14:14 ` Keir Fraser
2011-03-30 18:04 ` [PATCH 3 of 3] xentrace: remove unneeded debug printk Olaf Hering
2011-04-01 11: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=1301653939.9447.11.camel@elijah \
--to=george.dunlap@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).