Hi,
On 14/02/17 09:27, Dmitry V. Levin wrote:
> On Mon, Feb 13, 2017 at 04:47:05PM +, James Cowgill wrote:
>> On 13/02/17 14:40, Dmitry V. Levin wrote:
>>> On Mon, Jan 09, 2017 at 08:54:52PM +0300, Dmitry V. Levin wrote:
On Mon, Jan 09, 2017 at 05:31:37PM +, James Cowgill wrote:
>
On Mon, Feb 13, 2017 at 04:47:05PM +, James Cowgill wrote:
> Hi,
>
>
> On 13/02/17 14:40, Dmitry V. Levin wrote:
> > On Mon, Jan 09, 2017 at 08:54:52PM +0300, Dmitry V. Levin wrote:
> >> On Mon, Jan 09, 2017 at 05:31:37PM +, James Cowgill wrote:
> >>> On 06/01/17 00:51, Dmitry V. Levin wr
On 02/13/2017 08:47 AM, James Cowgill wrote:
>> Is there any simple way for MIPS o32 userspace to find out whether
>> the kernel is not a native MIPS o32? Something less hackish
>> than manually invoking a MIPS n64 syscall?
>
> uname -m is a bit less hackish:
>
> 32-bit kernel: $(uname -m) = mip
Hi,
On 13/02/17 14:40, Dmitry V. Levin wrote:
> On Mon, Jan 09, 2017 at 08:54:52PM +0300, Dmitry V. Levin wrote:
>> On Mon, Jan 09, 2017 at 05:31:37PM +, James Cowgill wrote:
>>> On 06/01/17 00:51, Dmitry V. Levin wrote:
On Tue, Jan 03, 2017 at 06:02:44PM +, James Cowgill wrote:
>
Hi,
On Mon, Jan 09, 2017 at 08:54:52PM +0300, Dmitry V. Levin wrote:
> On Mon, Jan 09, 2017 at 05:31:37PM +, James Cowgill wrote:
> > On 06/01/17 00:51, Dmitry V. Levin wrote:
> > > On Tue, Jan 03, 2017 at 06:02:44PM +, James Cowgill wrote:
> > >> On 20/12/16 00:36, Steve McIntyre wrote:
>
Hi,
On Mon, Jan 09, 2017 at 05:31:37PM +, James Cowgill wrote:
> On 06/01/17 00:51, Dmitry V. Levin wrote:
> > On Tue, Jan 03, 2017 at 06:02:44PM +, James Cowgill wrote:
> >> On 20/12/16 00:36, Steve McIntyre wrote:
> >>> On Tue, Dec 20, 2016 at 03:16:17AM +0300, Dmitry V. Levin wrote:
> >
Hi,
On 06/01/17 00:51, Dmitry V. Levin wrote:
> On Tue, Jan 03, 2017 at 06:02:44PM +, James Cowgill wrote:
>> On 20/12/16 00:36, Steve McIntyre wrote:
>>> On Tue, Dec 20, 2016 at 03:16:17AM +0300, Dmitry V. Levin wrote:
On Tue, Dec 20, 2016 at 12:50:29AM +0100, Nahim El Atmani wrote:
Hi,
On Tue, Jan 03, 2017 at 06:02:44PM +, James Cowgill wrote:
> On 20/12/16 00:36, Steve McIntyre wrote:
> > On Tue, Dec 20, 2016 at 03:16:17AM +0300, Dmitry V. Levin wrote:
> >> On Tue, Dec 20, 2016 at 12:50:29AM +0100, Nahim El Atmani wrote:
> >>> On Mon, 19 Dec 2016 18:30:29 +, Steve M
Happy New Year James!
On Tue, Jan 03, 2017 at 06:02:44PM +, James Cowgill wrote:
>On 20/12/16 00:36, Steve McIntyre wrote:
>>
>> Ah, OK. James Cowgill is my friendly local mips expert - let's see
>> what he thinks... :-)
>
>I've had a look and I think there is a kernel bug here - specifically
Hi,
On 20/12/16 00:36, Steve McIntyre wrote:
> On Tue, Dec 20, 2016 at 03:16:17AM +0300, Dmitry V. Levin wrote:
>> On Tue, Dec 20, 2016 at 12:50:29AM +0100, Nahim El Atmani wrote:
>>> On Mon, 19 Dec 2016 18:30:29 +, Steve McIntyre wrote:
I'm seeing test suite failures on mips[1], mipsel[2
On Tue, Dec 20, 2016 at 03:16:17AM +0300, Dmitry V. Levin wrote:
>Hi,
>
>On Tue, Dec 20, 2016 at 12:50:29AM +0100, Nahim El Atmani wrote:
>> Hi Steve,
>>
>> On Mon, 19 Dec 2016 18:30:29 +, Steve McIntyre wrote:
>> > I'm seeing test suite failures on mips[1], mipsel[2] and mips64el[3]
>> > on D
Hi,
On Tue, Dec 20, 2016 at 12:50:29AM +0100, Nahim El Atmani wrote:
> Hi Steve,
>
> On Mon, 19 Dec 2016 18:30:29 +, Steve McIntyre wrote:
> > I'm seeing test suite failures on mips[1], mipsel[2] and mips64el[3]
> > on Debian machines.
> >
> > The 32-bit builds are both showing issues with f
Hi Steve,
On Mon, 19 Dec 2016 18:30:29 +, Steve McIntyre wrote:
> I'm seeing test suite failures on mips[1], mipsel[2] and mips64el[3]
> on Debian machines.
>
> The 32-bit builds are both showing issues with fault injection. I
> can't follow what the code is meant to be doing here, so no
> id
On Wed, Dec 14, 2016 at 01:58:11PM +0300, Dmitry V. Levin wrote:
>Starting with version 4.13, strace follows the schedule of linux kernel
>and new versions of strace are released along with new version of linux
>kernel. So strace 4.15 is tagged and uploaded.
>
>This is the first strace release tha
Starting with version 4.13, strace follows the schedule of linux kernel
and new versions of strace are released along with new version of linux
kernel. So strace 4.15 is tagged and uploaded.
This is the first strace release that supports syscall fault injection,
the implementation is based on the
15 matches
Mail list logo