From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
qemu-devel@nongnu.org, pbonzini@redhat.com, fam@euphon.net
Cc: Thomas Huth <thuth@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [PATCH] esp.c: remove transfer size check from DMA DATA IN and DATA OUT transfers
Date: Tue, 16 Jul 2024 15:30:22 +0200 [thread overview]
Message-ID: <a47858bf-fa2e-4316-b48e-3927d6c14698@linaro.org> (raw)
In-Reply-To: <fbf76f1f-6efa-401f-a45d-ba4be739e51d@linaro.org>
On 16/7/24 10:56, Philippe Mathieu-Daudé wrote:
> On 16/7/24 08:46, Philippe Mathieu-Daudé wrote:
>> On 16/7/24 00:01, Mark Cave-Ayland wrote:
>>> On 15/07/2024 07:48, Philippe Mathieu-Daudé wrote:
>>>
>>>> On 14/7/24 00:42, Mark Cave-Ayland wrote:
>>>>> The transfer size check was originally added to prevent consecutive
>>>>> DMA TI
>>>>> commands from causing an assert() due to an existing SCSI request
>>>>> being in
>>>>> progress, but since the last set of updates
>>>>
>>>> [*]
>>>>
>>>>> this is no longer required.
>>>>>
>>>>> Remove the transfer size check from DMA DATA IN and DATA OUT
>>>>> transfers so
>>>>> that issuing a DMA TI command when there is no data left to
>>>>> transfer does
>>>>> not cause an assert() due to an existing SCSI request being in
>>>>> progress.
>>>>>
>>>>
>>>> [*] See commits f3ace75be8..78d68f312a
>>>>
>>>>> Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
>>>>> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2415
>>>>> ---
>>>>> hw/scsi/esp.c | 4 ++--
>>>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>>>>
>>>> Queued adding [*], thanks.
>>>
>>> Awesome, thanks Phil!
>>
>> I'm getting dubious timeout on the msys2 build on the SPARC target:
>> https://gitlab.com/philmd/qemu/-/jobs/7347774958
>>
>> qemu:qtest+qtest-sparc / qtest-sparc/qom-test time out (After 900.0
>> seconds)
>> 1/151 qemu:qtest+qtest-sparc / qtest-sparc/qom-test TIMEOUT
>> 900.38s exit status 1
>> qemu:qtest+qtest-sparc / qtest-sparc/device-introspect-test time out
>> (After 720.0 seconds)
>> 2/151 qemu:qtest+qtest-sparc / qtest-sparc/device-introspect-test
>> TIMEOUT 720.23s exit status 1
>> qemu:qtest+qtest-sparc / qtest-sparc/prom-env-test time out (After
>> 360.0 seconds)
>> 4/151 qemu:qtest+qtest-sparc / qtest-sparc/prom-env-test
>> TIMEOUT 360.17s exit status 1
>>
>> Not sure this patch is the culprit, but since only SPARC is affected,
>> likely. I'll retest without this patch.
>
> Same failure without this patch, so not this patch fault ;)
Actually I couldn't find any patch in my PR triggering this,
then noticed it is also happening on the main branch:
https://gitlab.com/qemu-project/qemu/-/jobs/7347517442
:/
prev parent reply other threads:[~2024-07-16 13:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 22:42 [PATCH] esp.c: remove transfer size check from DMA DATA IN and DATA OUT transfers Mark Cave-Ayland
2024-07-15 6:48 ` Philippe Mathieu-Daudé
2024-07-15 22:01 ` Mark Cave-Ayland
2024-07-16 6:46 ` Philippe Mathieu-Daudé
2024-07-16 8:56 ` Philippe Mathieu-Daudé
2024-07-16 13:30 ` Philippe Mathieu-Daudé [this message]
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=a47858bf-fa2e-4316-b48e-3927d6c14698@linaro.org \
--to=philmd@linaro.org \
--cc=fam@euphon.net \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.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).