From: "Alex Bennée" <alex.bennee@linaro.org>
To: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
Cc: shorne@gmail.com, amarkovic@wavecomp.com, qemu-devel@nongnu.org,
aurelien@aurel32.net, edgar.iglesias@gmail.com,
jcmvbkbc@gmail.com, michael@walle.cc,
Stefan Markovic <smarkovic@wavecomp.com>
Subject: Re: [Qemu-devel] [RFC PATCH 04/13] tests/tcg/mips: enable mips32-dsp/mips32-dspr2/mipsr5900 linux-user (WIP)
Date: Tue, 11 Dec 2018 12:17:50 +0000 [thread overview]
Message-ID: <87sgz41clt.fsf@linaro.org> (raw)
In-Reply-To: <CAL1e-=j1o_Sc0-xsgTq+0wsE1HC+p1_kEA5Op4Ub0D03J7juMA@mail.gmail.com>
Aleksandar Markovic <aleksandar.m.mail@gmail.com> writes:
> On Dec 10, 2018 4:29 PM, "Alex Bennée" <alex.bennee@linaro.org> wrote:
>>
>> Convert the existing tests to use our common cross build
>> infrastructure.
>>
>> [WIP: mips32r2 disabled to avoid name clash]
>> [WIP: mipsr5900 disabled due to clashing build flags]
>>
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>> ---
>> tests/tcg/mips/Makefile.target | 15 ++-
>> tests/tcg/mips/mips32-dsp/Makefile | 166 +++++----------------------
>> tests/tcg/mips/mips32-dspr2/Makefile | 83 +++-----------
>> tests/tcg/mips/mipsr5900/Makefile | 40 +++----
>> 4 files changed, 75 insertions(+), 229 deletions(-)
>>
>
> Thank you Alex for this initiative.
>
> For DSP, following MIPS CPUs in QEMU support DSP:
>
> DSP: 24KEc (MIPS32R2), 34Kf (MIPS32R2), 74Kf (MIPS32R2), mips64dspr2
> (MIPS64R2),
>
> DSP R2: mips64dspr2 (MIPS64R2),
That's why I'm confused by a mips32-dspr2 directory. Does that mean both
of those directories run on the 74Kf processor model (MIPS32R2)?
> (For simplicity, I didn't mention new nanoMIPS architecture, since your gcc
> for sure don't support it yet)
>
> In brackets, those are architectures that are usually required to be passed
> to gcc as its option, and that explains the switch involving MIPS64R2 for
> DSP R2.
>
> Whereas while starting QEMU, CPU name should be specified in -cpu switch.
>
> mips64dspr2 is a virtual cpu (doesn't model any real cpu) made specifically
> for DSP R2 testings, hence such odd name.
>
> Hopefully this clarifies some of your dilemmas.
>
> What are name clashes that you mention? Are they just related to
> filenames?
I think it is because there are a bunch of names in both mips32-dsp and
mips32-dspr2 that are the same. I thought that should be sorted by the
fact I only set the VPATH to tests/tcg/mips and added the tests
including their dir path but for some reason it wasn't working.
--
Alex Bennée
next prev parent reply other threads:[~2018-12-11 12:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 15:28 [Qemu-devel] [RFC PATCH 00/13] Enabling tcg/tests for xtensa, mips and cris Alex Bennée
2018-12-10 15:28 ` [Qemu-devel] [RFC PATCH 01/13] tests/tcg: add softmmu awareness to Makefile Alex Bennée
2018-12-11 13:38 ` Richard Henderson
2018-12-10 15:28 ` [Qemu-devel] [RFC PATCH 02/13] tests: enable tcg tests for softmmu Alex Bennée
2018-12-11 13:39 ` Richard Henderson
2018-12-10 15:28 ` [Qemu-devel] [RFC PATCH 03/13] tests/tcg: add QEMU_OPT option for test runner Alex Bennée
2018-12-11 13:39 ` Richard Henderson
2018-12-10 15:28 ` [Qemu-devel] [RFC PATCH 04/13] tests/tcg/mips: enable mips32-dsp/mips32-dspr2/mipsr5900 linux-user (WIP) Alex Bennée
2018-12-11 9:54 ` Aleksandar Markovic
2018-12-11 10:16 ` Aleksandar Markovic
2018-12-11 12:17 ` Alex Bennée [this message]
2018-12-11 13:45 ` Richard Henderson
2018-12-19 14:39 ` Aleksandar Markovic
2018-12-19 16:03 ` Alex Bennée
2018-12-27 11:22 ` Aleksandar Markovic
2018-12-28 10:28 ` Alex Bennée
2018-12-28 17:32 ` Aleksandar Markovic
2018-12-10 15:28 ` [Qemu-devel] [RFC PATCH 05/13] tests/tcg/mips: enable mips64 system tests (WIP) Alex Bennée
2018-12-27 18:40 ` Aleksandar Markovic
2018-12-27 18:42 ` Aleksandar Markovic
2018-12-10 15:28 ` [Qemu-devel] [RFC PATCH 06/13] tests/docker: add debian-xtensa-cross image Alex Bennée
2018-12-10 15:28 ` [Qemu-devel] [RFC PATCH 07/13] tests/tcg/xtensa: enable system tests Alex Bennée
2018-12-11 0:25 ` Max Filippov
2018-12-11 11:58 ` Alex Bennée
2018-12-11 12:32 ` Max Filippov
2018-12-10 15:28 ` [Qemu-devel] [RFC PATCH 08/13] tests/docker: add fedora-cris-cross compilers Alex Bennée
2018-12-10 15:28 ` [Qemu-devel] [RFC PATCH 09/13] tests/tcg: split cris tests into system and user mode Alex Bennée
2018-12-11 17:47 ` Alex Bennée
2018-12-10 15:28 ` [Qemu-devel] [RFC PATCH 10/13] tests/tcg/cris: cleanup sys.c Alex Bennée
2018-12-10 15:28 ` [Qemu-devel] [RFC PATCH 11/13] tests/tcg/cris: comment out the ccs test Alex Bennée
2019-01-04 14:00 ` Edgar E. Iglesias
2018-12-10 15:28 ` [Qemu-devel] [RFC PATCH 12/13] tests/tcg/cris: align mul operations Alex Bennée
2018-12-10 15:28 ` [Qemu-devel] [RFC PATCH 13/13] tests/tcg: enable cris system tests Alex Bennée
2019-01-04 13:58 ` [Qemu-devel] [RFC PATCH 00/13] Enabling tcg/tests for xtensa, mips and cris Edgar E. Iglesias
2019-01-04 14:03 ` Edgar E. Iglesias
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=87sgz41clt.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=aleksandar.m.mail@gmail.com \
--cc=amarkovic@wavecomp.com \
--cc=aurelien@aurel32.net \
--cc=edgar.iglesias@gmail.com \
--cc=jcmvbkbc@gmail.com \
--cc=michael@walle.cc \
--cc=qemu-devel@nongnu.org \
--cc=shorne@gmail.com \
--cc=smarkovic@wavecomp.com \
/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).