[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Mips-arc tests ever work?
From: |
John Paul Adrian Glaubitz |
Subject: |
Re: Mips-arc tests ever work? |
Date: |
Sat, 5 Dec 2020 21:28:05 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 |
On 12/5/20 8:10 PM, Glenn Washburn wrote:
>> I'm running manual tests for all architectures before each release.
>
> What exactly are manual tests? Is that running manually the tests for
> that target? (ie "make check" for that target)
Yes. I'm test-compiling GRUB natively, run "make check" and also perform
test installations in some cases.
> Also what version of qemu are you running to do the tests?
I'm performing all tests on real hardware. I have access to all architectures
supported by GRUB either through my personal hardware zoo, the Debian project
of which I am member of or the GCC compile farm for which I am also providing
hardware.
You are free to register for the GCC compile farm and use it yourself [1].
>> I could not find any reference to "indy" in the qemu git log. Are you
>> sure it was ever officially supported? I assume the tests here were
>> run on real hardware.
>
> Take a look in "tests/util/grub-shell.in" and you'll find the offending
> test code in grub. I have no clue either way whether it was ever
> supported, but someone obviously did because its in the test code. And
> that someone might be Vladimir (phcoder) who committed the code. This
> is why I'm wondering if it ever worked.
Maybe he used a fork of qemu for these tests.
>>> According to wikipedia the SGI Indy originally used R4k processors.
>>> So would machine type mips be the one to use since its description
>>> says "mips r4k platform"?
>>
>> No, that was a different, generic machine type, see [1].
>
> I'm confused by this response. My qemu doesn't list a "r4k" machine
> type and its version 4.2.1. The machine type "mips" says its the r4k
> platform, but that doesn't look like what's being removed in that
> commit. Reviewing the hw/mips/Kconfig, it looks like the machine types
> have changed a lot since 4.2.1, so maybe it was renamed to "r4k"
> (haven't checked yet). However if it was renamed and is being removed,
> that's going to cause further problems (when/if we use qemu 5.2 for
> testing) because grub-shell is using the "mips" machine type for
> "mips-qemu_mips" and "mipsel-qemu_mips".
Well, either way, the r4k machine no longer exists in QEMU 5.2.
>>> So can anyone familiar with this tell me an appropriate machine
>>> type of the above listed to use instead of indy? Perhaps Vladimir
>>> who committed that code can chime in?
>
> Ultimately, I just want to know what machine should I use if not indy
> for the "mips-arc" target? I know very little about mips and what an
> appropriate machine type would be for emulating this target.
I guess "malta" would work, too.
Adrian
> [1] https://gcc.gnu.org/wiki/CompileFarm
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913