Probing for native availability of isel from userspace

2012-09-21 Thread malc
Hello, Is it possible to determine if _native_ isel is available from userspace somehow? So far my searches on the web and within kernel (headers)/glibc were fruitless (aux vectors, cpu_user_features), few people people (Hollis Blanchard, Richard Henderson) suggested PPC_FEATURE_ARCH_2_06, but Po

Re: Probing for native availability of isel from userspace

2012-09-22 Thread malc
On Sat, 22 Sep 2012, Segher Boessenkool wrote: > > Is it possible to determine if _native_ isel is available from userspace > > somehow? > > Just try to execute one and catch the SIGILL? > Unfortunately my kernel emulates ISEL for me in this case, so i don't get any SIGILLs. -- mailto:av1...@

Re: Probing for native availability of isel from userspace

2012-09-22 Thread malc
On Sat, 22 Sep 2012, Gabriel Paubert wrote: > On Sat, Sep 22, 2012 at 02:12:42PM +0400, malc wrote: > > On Sat, 22 Sep 2012, Segher Boessenkool wrote: > > > > > > Is it possible to determine if _native_ isel is available from userspace > > > > somehow? &

Re: Probing for native availability of isel from userspace

2012-09-22 Thread malc
On Sun, 23 Sep 2012, Benjamin Herrenschmidt wrote: > On Sat, 2012-09-22 at 21:08 +0200, Segher Boessenkool wrote: > > > Thanks for suggestion, but i'd rather not play with heuristics. > > > > Have a look at /sys/kernel/debug/powerpc/emulated_instructions/ then? > > Userspace should *NEVER* rely

Re: Probing for native availability of isel from userspace

2012-09-24 Thread malc
On Tue, 25 Sep 2012, Benjamin Herrenschmidt wrote: > On Mon, 2012-09-24 at 18:55 -0500, Scott Wood wrote: > > The ISA says that isel is "Category: Phased-In (sV2.06)" -- are there > > any 2.06 chips that don't have it? > > I believe "malc" is i

Re: Lock-up on PPC64

2009-02-22 Thread malc
On Wed, 7 Jan 2009, malc wrote: > On Wed, 7 Jan 2009, Benjamin Herrenschmidt wrote: > > > > > > As you wish :) I've written some ad-hoc stuff in the failing path which > > > manually triggers sysrq and then sends the klogctl output via network >

Lock-up on PPC64

2008-12-25 Thread malc
Hello, Benjamin Herrenschmidt asked to re-report this issue to linuxppc-dev and here it is. [original LKML message http://lkml.org/lkml/2008/12/21/105] Synopsis Plain/non-root userspace application which doesn't interface with any weird out-of/in-tree drivers manages to lock-up a PS3 machine ru

Re: Lock-up on PPC64

2008-12-27 Thread malc
On Thu, 25 Dec 2008, Benjamin Herrenschmidt wrote: On Wed, 2008-12-24 at 03:08 +0300, m...@pulsesoft.com wrote: Ken Moffat writes: On Tue, Dec 23, 2008 at 06:04:45AM +0300, m...@pulsesoft.com wrote: [..snip..] Thanks for the reference, but i'm sure, now more than ever, that bad memory h

Re: Lock-up on PPC64

2009-01-05 Thread malc
On Mon, 5 Jan 2009, Michael Ellerman wrote: On Sun, 2008-12-28 at 03:45 +0300, malc wrote: On Thu, 25 Dec 2008, Benjamin Herrenschmidt wrote: On Wed, 2008-12-24 at 03:08 +0300, m...@pulsesoft.com wrote: Ken Moffat writes: On Tue, Dec 23, 2008 at 06:04:45AM +0300, m...@pulsesoft.com wrote

Re: Lock-up on PPC64

2009-01-06 Thread malc
On Tue, 6 Jan 2009, Benjamin Herrenschmidt wrote: On Mon, 2009-01-05 at 19:34 +0300, malc wrote: Before this change (atleast) mono_handle_native_sigsegv was executed (before machine locks-up hard) after the change this code path is never touched. The fact that machine locks up hard and not

Re: Lock-up on PPC64

2009-01-06 Thread malc
On Wed, 7 Jan 2009, Benjamin Herrenschmidt wrote: As you wish :) I've written some ad-hoc stuff in the failing path which manually triggers sysrq and then sends the klogctl output via network and here it is: Allright, something's unclear to me. What do you mean by the system goes down then ?