From: Michael Ellerman <michael@ellerman.id.au>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: Linux/PPC Development <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] powerpc: Keep track of emulated instructions
Date: Sat, 04 Apr 2009 15:37:28 +1100 [thread overview]
Message-ID: <1238819848.9595.25.camel@localhost> (raw)
In-Reply-To: <alpine.LRH.2.00.0904031404450.32353@vixen.sonytel.be>
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
On Fri, 2009-04-03 at 14:08 +0200, Geert Uytterhoeven wrote:
> Hi Ben, Kumar,
>
> Finally (after ca. 1.5 years), he're an updated version of my patch to keep
> track of emulated instructions. In the light of Kumar's `Emulate enough of SPE
> instructions to make gcc happy' patch, he probably also wants to keep track of
> the actual runtime overhead.
>
> Changes since last version:
> - arch/powerpc/kernel/sysfs.c is now compiled on ppc32, so we can provide
> counters in sysfs on ppc32, too,
> - WARN_EMULATED() is a no-op if CONFIG_SYSCTL is disabled,
> - Add warnings for altivec,
> - Add warnings for recently introduced emulation of vsx and isel
> instructions.
You don't count instructions that fall through to the bottom of
fix_alignment()?
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-04-04 4:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 12:08 [PATCH] powerpc: Keep track of emulated instructions Geert Uytterhoeven
2009-04-03 14:15 ` Kumar Gala
2009-04-06 12:33 ` Geert Uytterhoeven
2009-04-06 22:43 ` Michael Neuling
2009-04-07 7:26 ` Geert Uytterhoeven
2009-04-07 8:05 ` Michael Neuling
2009-04-29 12:43 ` Geert Uytterhoeven
2009-04-04 4:37 ` Michael Ellerman [this message]
2009-04-06 12:30 ` Geert Uytterhoeven
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=1238819848.9595.25.camel@localhost \
--to=michael@ellerman.id.au \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=linuxppc-dev@ozlabs.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 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.