From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Paul Mackerras <paulus@samba.org>,
Anton Blanchard <anton@samba.org>,
ahuja@austin.ibm.com,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PPC64 collect and export low-level cpu usage statistics
Date: Thu, 10 Feb 2005 10:17:34 +1100 [thread overview]
Message-ID: <1107991054.7734.150.camel@gaston> (raw)
In-Reply-To: <20050209150643.60812d3f.akpm@osdl.org>
On Wed, 2005-02-09 at 15:06 -0800, Andrew Morton wrote:
> Paul Mackerras <paulus@samba.org> wrote:
> >
> > POWER5 machines have a per-hardware-thread register which counts at a
> > rate which is proportional to the percentage of cycles on which the
> > cpu dispatches an instruction for this thread (if the thread gets all
> > the dispatch cycles it counts at the same rate as the timebase
> > register). This register is also context-switched by the hypervisor.
> > Thus it gives a fine-grained measure of the actual cpu usage by the
> > thread over time.
> >
> > This patch adds code to read this register every timer interrupt and
> > on every context switch.
>
> fyi: This patch consumes another entry from thread_struct.pad[].
> ppc64-implement-a-vdso-and-use-it-for-signal-trampoline.patch consumes two
> more entries, so with both patches, you have none left.
Why couldn't we extend the structure ? That would at worse break modules
binary compatibility, who cares ? :)
Those pads are just stuff that aren't used any more, and back then, when
removing them, we did care about modules binary compat...
Anyways, I don't think there's anything to worry about at this point.
Paul ?
Ben.
prev parent reply other threads:[~2005-02-09 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 21:56 [PATCH] PPC64 collect and export low-level cpu usage statistics Paul Mackerras
2005-02-09 23:06 ` Andrew Morton
2005-02-09 23:17 ` Benjamin Herrenschmidt [this message]
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=1107991054.7734.150.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=ahuja@austin.ibm.com \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
/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