From: Ben Thomas <bthomas@virtualiron.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Allow building with perfc and perfc_arrays
Date: Thu, 16 Feb 2006 17:17:47 -0500 [thread overview]
Message-ID: <43F4FA0B.2010309@virtualiron.com> (raw)
In-Reply-To: <20060216212643.GS3490@sorel.sous-sol.org>
Hi,
Well, I did use the phrase "simple-minded". It seemed like
adequate warning. ;-)
My goal was to get it compiling and out of my way so that
I could work on something else. This was purely annoying and
I spent very little time on it. Then, once I got it compiling,
the guilt-gene kicked in and I thought I should submit the
changes.
Your changes are more complete, and I like them better.
(Now, if I could manage to spend the time to package up other
changes that I've made ...)
Thanks,
-b
Chris Wright wrote:
> * Ben Thomas (bthomas@virtualiron.com) wrote:
>
>>Attempts to build with either perfc or perfc_arrays fails. Some of
>>this is specific to the platform (eg, __x86_64__). Add simple-minded
>>fixes to allow building with these options.
>>
>>This patch resolves these issues and now builds on i386 and x86_64
>
>
> I was just doing similar. Only real difference I had was just using
> char in the dom0_perfc_desc instead of the char* cast.
>
> typedef struct dom0_perfc_desc {
> - uint8_t name[80]; /* name of perf counter */
> + char name[80]; /* name of perf counter */
>
> And a typo fix, which you accidentally propagate.
>
> +PERFCOUNTER_CPU(apshot_pages, "apshot_pages")
>
> I had simply done:
>
> - perfc_decr(apshot_pages);
> + perfc_decr(snapshot_pages);
>
> Accidental conversion to percpu counter of a couple of these. And,
> finally, this isn't quite enough for PAE.
>
> Here's my patch, mind taking a double check?
>
> thanks,
> -chris
next prev parent reply other threads:[~2006-02-16 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 19:52 [PATCH] Allow building with perfc and perfc_arrays Ben Thomas
2006-02-16 21:26 ` Chris Wright
2006-02-16 22:17 ` Ben Thomas [this message]
2006-02-16 22:51 ` Chris Wright
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=43F4FA0B.2010309@virtualiron.com \
--to=bthomas@virtualiron.com \
--cc=chrisw@sous-sol.org \
--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.