All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gabriel Paubert <paubert@iram.es>
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 17:58:37 +1000	[thread overview]
Message-ID: <1348473517.1132.87.camel@pasglop> (raw)
In-Reply-To: <20120924075546.GA4263@visitor2.iram.es>

On Mon, 2012-09-24 at 09:55 +0200, Gabriel Paubert wrote:
> On Sun, Sep 23, 2012 at 03:46:06AM +0200, Segher Boessenkool wrote:
> > Why does the kernel emulate this, btw?  I can see emulation is useful
> > for running older binaries, for instructions that have been removed
> > from the architecture; but for newly added instructions, or optional
> > instructions, it hurts more than it helps?
> 
> Indeed. I also don't understand why mfpvr is emulated. That's the kind
> of information that should be passed to the executables through auxiliary
> vectors. After all, you can (or could at least) compile a kernel without
> Altivec support and run it on a processor with Altivec.
> 
> Therefore, whether Altivec is supported or not, is a matter of
> processor and kernel options. Provide this information through
> the auxiliary vector and the problem is solved.

Which we do. mfpvr is available as a fallback (essentially because if we
don't do it somebody's going to parse /proc/cpuinfo which is arguably
worse :-)

We should definitely advertise the availability of isel.

Cheers,
Ben.

  reply	other threads:[~2012-09-24  7:58 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 [this message]
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
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=1348473517.1132.87.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=av1474@comtv.ru \
    --cc=hollis@penguinppc.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paubert@iram.es \
    /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.