All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: malc <av1474@comtv.ru>,
	linuxppc-dev@lists.ozlabs.org, hollis@penguinppc.org
Subject: Re: Probing for native availability of isel from userspace
Date: Mon, 24 Sep 2012 18:55:09 -0500	[thread overview]
Message-ID: <1348530909.25867.29@snotra> (raw)
In-Reply-To: <35A5B006-1E4E-4355-A6A4-CA5F7371D21C@kernel.crashing.org> (from segher@kernel.crashing.org on Sat Sep 22 20:46:06 2012)

On 09/22/2012 08:46:06 PM, Segher Boessenkool wrote:
>>> Have a look at /sys/kernel/debug/powerpc/emulated_instructions/ =20
>>> then?
>>=20
>> Userspace should *NEVER* rely on the content of debugfs, it will =20
>> change
>> with time, it is not a guaranteed ABI, it's purely for people to look
>> at... for debugging.
>=20
> malc didn't say what he wants it for...  People are in userspace as
> well ;-)
>=20
>> At this stage I would recommend using arch 2.06 as your key/trigger =20
>> and
>> either add a handful of known PVR values (mfpvr is emulated) for =20
>> other
>> CPUs you know support it (there shouldn't be that many), or just do =20
>> the
>> heuristic :-(

The ISA says that isel is "Category: Phased-In (sV2.06)" -- are there =20
any 2.06 chips that don't have it?

> That's for 64-bit; another good option for 64-bit is to just never use
> isel, it hardly ever buys you anything.  It is much more useful on the
> (older) 32-bit cores that support it.

Why is it more useful on 32-bit?  If you're referring to the =20
performance of specific cores rather than some architectural thing, =20
maybe that's true with some chips, but on the Freescale side I'd be =20
surprised if e5500 were much different from e500v2 in that regard.

-Scott=

  parent reply	other threads:[~2012-09-24 23:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21 20:05 Probing for native availability of isel from userspace malc
2012-09-22  7:26 ` Segher Boessenkool
2012-09-22 10:12   ` malc
2012-09-22 10:21     ` Gabriel Paubert
2012-09-22 15:37       ` malc
2012-09-22 16:13         ` David Gibson
2012-09-22 19:08         ` Segher Boessenkool
2012-09-22 19:55           ` Benjamin Herrenschmidt
2012-09-22 20:17             ` malc
2012-09-23  1:46             ` Segher Boessenkool
2012-09-24  7:55               ` Gabriel Paubert
2012-09-24  7:58                 ` Benjamin Herrenschmidt
2012-09-24  8:06                   ` Gabriel Paubert
2012-09-24  9:41                     ` Benjamin Herrenschmidt
2012-09-25 13:17                       ` Segher Boessenkool
2012-09-25 20:59                         ` Benjamin Herrenschmidt
2012-09-26  0:17                           ` Kumar Gala
2012-09-24 23:55               ` Scott Wood [this message]
2012-09-25  0:32                 ` Benjamin Herrenschmidt
2012-09-25  0:40                   ` Scott Wood
2012-09-25  0:47                   ` malc
2012-09-25  0:50                     ` Scott Wood
2012-09-25 13:31                 ` Segher Boessenkool

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=1348530909.25867.29@snotra \
    --to=scottwood@freescale.com \
    --cc=av1474@comtv.ru \
    --cc=hollis@penguinppc.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=segher@kernel.crashing.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.