All of lore.kernel.org
 help / color / mirror / Atom feed
From: BALATON Zoltan via <qemu-devel@nongnu.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Huacai Chen" <zltjiangshi@gmail.com>,
	"Thomas Huth" <thuth@redhat.com>,
	"Daniel P . Berrange" <berrange@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
	qemu-devel@nongnu.org,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
	"Cleber Rosa" <crosa@redhat.com>,
	"Huacai Chen" <chenhc@lemote.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 0/6] tests/acceptance: Test the Fuloong 2E machine
Date: Sun, 25 Oct 2020 15:30:07 +0100 (CET)	[thread overview]
Message-ID: <ed6d6b59-cd2c-a59-5d8-4c93c7fa88ef@eik.bme.hu> (raw)
In-Reply-To: <d2851fba-040c-9f39-ccf7-2d22b862ec2b@amsat.org>

[-- Attachment #1: Type: text/plain, Size: 3559 bytes --]

On Sun, 25 Oct 2020, Philippe Mathieu-Daudé wrote:
> On 10/25/20 12:18 PM, Mark Cave-Ayland wrote:
>> On 21/10/2020 11:50, Philippe Mathieu-Daudé wrote:
>> 
>>> This series add tests for the MIPS Fuloong 2E machine.
>>> 
>>> I have been using these tests for over 1 year now.
>>> After recent discussions with Huacai and Mark regarding
>>> how to contribute tests for machines using private blob,
>>> I think it is time to publish this series, to see how
>>> the final part will be discussed, as it tests a blob
>>> which Lemote company doesn't publish the sources. The
>>> binary is know to work and has been used for various
>>> years on real hardware. Its MD5 is also know (I am not
>>> using SHA-1 because it has been published with MD5).
>>> 
>>> The idea is to be able to share tests without infringing
>>> licenses issues.
>>> 
>>> Please comment :)
>>> 
>>> Phil.
>>> 
>>> Philippe Mathieu-Daudé (6):
>>>    tests/acceptance: Remove unused import
>>>    tests/acceptance: Use .ppm extention for Portable PixMap files
>>>    tests/acceptance: Extract tesseract_available() helper in new
>>>      namespace
>>>    tests/acceptance: Introduce tesseract_ocr() helper
>>>    tests/acceptance: Test Linux on the Fuloong 2E machine
>>>    tests/acceptance: Test PMON on the Fuloong 2E machine
>>> 
>>>   MAINTAINERS                                |   1 +
>>>   tests/acceptance/machine_m68k_nextcube.py  |  51 ++---------
>>>   tests/acceptance/machine_mips_fuloong2e.py | 101 +++++++++++++++++++++
>>>   tests/acceptance/tesseract_utils.py        |  46 ++++++++++
>>>   4 files changed, 158 insertions(+), 41 deletions(-)
>>>   create mode 100644 tests/acceptance/machine_mips_fuloong2e.py
>>>   create mode 100644 tests/acceptance/tesseract_utils.py
>> 
>> In general this looks good: certainly I don't see any reason why the 
>> tesseract_ocr helper changes shouldn't be merged, since I expect that this 
>> is something that will be used more in future.
>> 
>> Looking at the fuloong test it seems that it stops fairly early in the 
>> kernel boot: one of the problems that Zoltan's VIA southbridge patches were 
>> trying to solve earlier in the year was because of problems with PCI IRQ 
>> routing, so it would be nice to include a small OS image that can be used 
>> to boot to userspace to ensure that such problems can be detected in 
>> future.
>
> The Linux tests (ab)use of the rescue image prepared for the Yeeloong
> machine which we don't model (Loongson 2F CPU, 1GB of DRAM). The kernel
> triggers DATA ABORT while accessing >256MB because we do not model
> mapping more than 256MB :/ (The Fuloong comes with 512MB extensible to 1GB). 
> I have a branch adding that but had the idea nobody was interested
> in the Fuloong 2E so I didn't insist (I have more interest in embedded
> 32-bit CPUs). I might try to post it after the release, as it makes this
> test complete.

I've noticed that missing high RAM when cleaning up SPD EEPROMs and addded 
a FIXME comment but did't know MIPS enough to attemt to fix it. Anyway I'm 
also only interested in fuloong2e as a test case for the devices also used 
by Pegasos2 (that I'll need to update and clean up to submit eventually) 
but not beyond that.

I haven't seen these patches before, so I've spotted only now that your 
test case uses -vga std. Shouldn't it work with ati-vga,model=rv100 which 
I think is the default for this machine and that's what the pmon firmware 
expects and has a driver for?

Regards,
BALATON Zoltan

  reply	other threads:[~2020-10-25 14:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-21 10:50 [PATCH 0/6] tests/acceptance: Test the Fuloong 2E machine Philippe Mathieu-Daudé
2020-10-21 10:50 ` [PATCH 1/6] tests/acceptance: Remove unused import Philippe Mathieu-Daudé
2020-10-24  6:58   ` Thomas Huth
2020-10-21 10:50 ` [PATCH 2/6] tests/acceptance: Use .ppm extention for Portable PixMap files Philippe Mathieu-Daudé
2020-10-24  6:24   ` Thomas Huth
2020-10-21 10:50 ` [PATCH 3/6] tests/acceptance: Extract tesseract_available() helper in new namespace Philippe Mathieu-Daudé
2020-10-24  6:31   ` Thomas Huth
2020-10-21 10:50 ` [PATCH 4/6] tests/acceptance: Introduce tesseract_ocr() helper Philippe Mathieu-Daudé
2020-10-24  6:35   ` Thomas Huth
2020-10-24  6:40     ` Thomas Huth
2020-10-24  7:37       ` Philippe Mathieu-Daudé
2020-10-24 17:40         ` Philippe Mathieu-Daudé
2020-10-26  6:09           ` Thomas Huth
2020-10-21 10:50 ` [PATCH 5/6] tests/acceptance: Test Linux on the Fuloong 2E machine Philippe Mathieu-Daudé
2020-10-21 10:50 ` [PATCH 6/6] tests/acceptance: Test PMON " Philippe Mathieu-Daudé
2020-10-25 11:18 ` [PATCH 0/6] tests/acceptance: Test " Mark Cave-Ayland
2020-10-25 12:22   ` Philippe Mathieu-Daudé
2020-10-25 14:30     ` BALATON Zoltan via [this message]
2020-10-26  8:50 ` Philippe Mathieu-Daudé
2020-10-26 17:20   ` Philippe Mathieu-Daudé

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=ed6d6b59-cd2c-a59-5d8-4c93c7fa88ef@eik.bme.hu \
    --to=qemu-devel@nongnu.org \
    --cc=alex.bennee@linaro.org \
    --cc=balaton@eik.bme.hu \
    --cc=berrange@redhat.com \
    --cc=chenhc@lemote.com \
    --cc=crosa@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=philmd@redhat.com \
    --cc=thuth@redhat.com \
    --cc=wainersm@redhat.com \
    --cc=zltjiangshi@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.