From: "Maciej W. Rozycki" <macro@imgtec.com>
To: Paul Burton <paul.burton@imgtec.com>
Cc: Ralf Baechle <ralf@linux-mips.org>, <linux-mips@linux-mips.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/4] MIPS: Fix ISA I/II FP signal context offsets
Date: Tue, 1 Nov 2016 11:49:56 +0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1611011131120.31859@tp.orcam.me.uk> (raw)
In-Reply-To: <1814661.4I5xJD6gaP@np-p-burton>
On Tue, 1 Nov 2016, Paul Burton wrote:
> BTW, do you have a feel for whether there's a good r2k/r3k platform (ideal
> would be some software emulator if any are good enough) that we could hook up
> to our continuous integration system? That would help us to catch any
> regressions like this in future before they hit mainline.
I know about no such platform I'm afraid.
QEMU does not have the R2k/R3k exception/MMU/cache model and implementing
that would be a considerable effort I see no volunteers for. I haven't
heard of any other simulator which might be closer to implementing that
model.
As to using real hardware -- I might be the closest myself to be capable
of doing some automated testing as I have an R3k machine in my home lab
wired for remote control. It could track Ralf's `mips-for-linux-next'
branch and watch out for regressions, by trying to build and boot kernels
automatically on a regular basis; maybe doing some further validation
even, such as running GCC or glibc regression testing. But while the
target is ready I'm still missing the host-side setup, which I haven't
completed. I don't think there's any other hardware readily available
which could be hooked somewhere.
So for the time being I think we need to continue relying on people
spotting issues by hand. I think we've been doing pretty good overall.
Thanks for your review.
Maciej
WARNING: multiple messages have this Message-ID (diff)
From: "Maciej W. Rozycki" <macro@imgtec.com>
To: Paul Burton <paul.burton@imgtec.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] MIPS: Fix ISA I/II FP signal context offsets
Date: Tue, 1 Nov 2016 11:49:56 +0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1611011131120.31859@tp.orcam.me.uk> (raw)
Message-ID: <20161101114956.DSBuH1ca09oQNmjU50l5MaIaW3D8hQMxu5pn0M-DdL0@z> (raw)
In-Reply-To: <1814661.4I5xJD6gaP@np-p-burton>
On Tue, 1 Nov 2016, Paul Burton wrote:
> BTW, do you have a feel for whether there's a good r2k/r3k platform (ideal
> would be some software emulator if any are good enough) that we could hook up
> to our continuous integration system? That would help us to catch any
> regressions like this in future before they hit mainline.
I know about no such platform I'm afraid.
QEMU does not have the R2k/R3k exception/MMU/cache model and implementing
that would be a considerable effort I see no volunteers for. I haven't
heard of any other simulator which might be closer to implementing that
model.
As to using real hardware -- I might be the closest myself to be capable
of doing some automated testing as I have an R3k machine in my home lab
wired for remote control. It could track Ralf's `mips-for-linux-next'
branch and watch out for regressions, by trying to build and boot kernels
automatically on a regular basis; maybe doing some further validation
even, such as running GCC or glibc regression testing. But while the
target is ready I'm still missing the host-side setup, which I haven't
completed. I don't think there's any other hardware readily available
which could be hooked somewhere.
So for the time being I think we need to continue relying on people
spotting issues by hand. I think we've been doing pretty good overall.
Thanks for your review.
Maciej
next prev parent reply other threads:[~2016-11-01 11:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 16:24 [PATCH 0/4] MIPS I/II FP signal context handling fixes Maciej W. Rozycki
2016-10-31 16:24 ` Maciej W. Rozycki
2016-10-31 16:25 ` [PATCH 1/4] MIPS: Fix ISA I FP sigcontext access violation handling Maciej W. Rozycki
2016-10-31 16:25 ` Maciej W. Rozycki
2016-11-01 9:27 ` Paul Burton
2016-11-01 9:27 ` Paul Burton
2016-10-31 16:26 ` [PATCH 2/4] MIPS: Remove FIR from ISA I FP signal context Maciej W. Rozycki
2016-10-31 16:26 ` Maciej W. Rozycki
2016-10-31 16:27 ` [PATCH 3/4] MIPS: Fix ISA I/II FP signal context offsets Maciej W. Rozycki
2016-10-31 16:27 ` Maciej W. Rozycki
2016-11-01 9:31 ` Paul Burton
2016-11-01 9:31 ` Paul Burton
2016-11-01 11:49 ` Maciej W. Rozycki [this message]
2016-11-01 11:49 ` Maciej W. Rozycki
2016-10-31 16:27 ` [PATCH 4/4] MIPS: Correct MIPS I FP sigcontext layout Maciej W. Rozycki
2016-10-31 16:27 ` Maciej W. Rozycki
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=alpine.DEB.2.00.1611011131120.31859@tp.orcam.me.uk \
--to=macro@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=paul.burton@imgtec.com \
--cc=ralf@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).