From: Helge Deller <deller@gmx.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: deller@kernel.org, qemu-devel@nongnu.org,
Richard Henderson <richard.henderson@linaro.org>,
Sven Schnelle <svens@stackframe.org>,
Jason Wang <jasowang@redhat.com>
Subject: Re: [PULL 00/12] Hppa64 patches
Date: Tue, 13 Feb 2024 12:00:54 +0100 [thread overview]
Message-ID: <ebcf7d0b-17d8-409d-a07b-0399d7071eac@gmx.de> (raw)
In-Reply-To: <CAFEAcA_CQ6PKHyvg9qKeWDJpkbTu8rv=TCm3GemJmKQCrjPNuA@mail.gmail.com>
On 2/13/24 10:10, Peter Maydell wrote:
> On Mon, 12 Feb 2024 at 23:04, Helge Deller <deller@gmx.de> wrote:
>>
>> On 2/12/24 22:16, Peter Maydell wrote:
>>> This fails "make check", eg:
>>> https://gitlab.com/qemu-project/qemu/-/jobs/6154451100
>>>
>>> because when the qom-test etc tests run qemu-system-hppa, it
>>> barfs with "qemu-system-hppa: no firmware provided".
>>>
>>> That kind of firmware check needs to not fire when
>>> using the qtest accel.
>>
>> Ok. But how do people usually work around this kind of issue?
>> Test if the qtest accel is in use?
>> Ignore if the firmware can't be loaded?
>> Any hint would be great!
>
> There's a qtest_enabled() function -- see eg hw/mips/malta.c
> for an example of skipping the "fail on no firmware" check
> when it's enabled. (There are a bunch of others in the tree too.)
Yes, I found that....
I've used that function in the latest pull request which I sent...
Thanks!
Helge
next prev parent reply other threads:[~2024-02-13 11:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 12:28 [PULL 00/12] Hppa64 patches deller
2024-02-11 12:28 ` [PULL 01/12] disas/hppa: Add disassembly for qemu specific instructions deller
2024-02-11 12:28 ` [PULL 02/12] target/hppa: Add "diag 0x101" for console output support deller
2024-02-11 12:29 ` [PULL 03/12] hw/pci-host/astro: Avoid aborting on access failure deller
2024-02-11 12:29 ` [PULL 04/12] hw/pci-host/astro: Implement Hard Fail and Soft Fail mode deller
2024-02-11 12:29 ` [PULL 05/12] lasi: allow access to LAN MAC address registers deller
2024-02-11 12:29 ` [PULL 06/12] target/hppa: Implement do_transaction_failed handler for I/O errors deller
2024-02-11 12:29 ` [PULL 07/12] lasi: Add reset I/O ports for LASI audio and FDC deller
2024-02-11 12:29 ` [PULL 08/12] target/hppa: Allow read-access to PSW with rsm 0, reg instruction deller
2024-02-11 12:29 ` [PULL 09/12] target/hppa: PDC_BTLB_INFO uses 32-bit ints deller
2024-02-11 12:29 ` [PULL 10/12] hw/net/tulip: add chip status register values deller
2024-02-11 12:29 ` [PULL 11/12] target/hppa: Update SeaBIOS-hppa to version 16 deller
2024-02-11 18:48 ` Michael Tokarev
2024-02-11 18:49 ` Michael Tokarev
2024-02-12 23:45 ` Helge Deller
2024-02-11 12:29 ` [PULL 12/12] hw/hppa/machine: Load 64-bit firmware on 64-bit machines deller
2024-02-12 21:16 ` [PULL 00/12] Hppa64 patches Peter Maydell
2024-02-12 23:04 ` Helge Deller
2024-02-13 9:10 ` Peter Maydell
2024-02-13 11:00 ` Helge Deller [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-12 23:47 deller
2024-02-13 15:50 ` Peter Maydell
2024-02-13 18:09 ` Michael Tokarev
2024-02-13 19:16 ` Helge Deller
2024-02-14 9:07 ` Michael Tokarev
2024-02-14 14:58 ` Helge Deller
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=ebcf7d0b-17d8-409d-a07b-0399d7071eac@gmx.de \
--to=deller@gmx.de \
--cc=deller@kernel.org \
--cc=jasowang@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=svens@stackframe.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).