qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Olivier Danet <odanet@caramail.com>
Cc: Blue Swirl <blauwirbel@gmail.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Artyom Tarasenko <atar4qemu@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] Sun4m : SCSI ESP controller
Date: Sun, 23 Feb 2014 16:50:39 +0000	[thread overview]
Message-ID: <530A26DF.8030900@ilande.co.uk> (raw)
In-Reply-To: <5305C3B2.7020800@ilande.co.uk>

On 20/02/14 08:58, Mark Cave-Ayland wrote:

> On 16/02/14 23:13, Olivier Danet wrote:
>
>> Two small fixes for the ESP (AM53C94) SCSI controller
>>
>> * Signal the end of the DMA transfer after a SCSI command.
>>
>> * The status register (RSTAT) is cleared after reading the interrupt
>> status register (RINTR), except for the TC bit (=Count To Zero) and the
>> scsi phase bits, which mirror SCSI signals levels.
>>
>> Fixes the bug "esp0: !TC on DATA XFER" with NetBSD
>> https://bugs.launchpad.net/qemu/+bug/1055090
>>
>> Signed-off-by: Olivier Danet <odanet@caramail.com>
>> ---
>> hw/scsi/esp.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/hw/scsi/esp.c b/hw/scsi/esp.c
>> index 2d150bf..5e91077 100644
>> --- a/hw/scsi/esp.c
>> +++ b/hw/scsi/esp.c
>> @@ -246,6 +246,7 @@ static void esp_do_dma(ESPState *s)
>> s->cmdlen = 0;
>> s->do_cmd = 0;
>> do_cmd(s, s->cmdbuf);
>> + esp_dma_done(s);
>> return;
>> }
>> if (s->async_len == 0) {
>> @@ -417,10 +418,9 @@ uint64_t esp_reg_read(ESPState *s, uint32_t saddr)
>> except TC */
>> old_val = s->rregs[ESP_RINTR];
>> s->rregs[ESP_RINTR] = 0;
>> - s->rregs[ESP_RSTAT] &= ~STAT_TC;
>> s->rregs[ESP_RSEQ] = SEQ_CD;
>> esp_lower_irq(s);
>> -
>> + s->rregs[ESP_RSTAT] &= STAT_TC | STAT_MI;
>> return old_val;
>> default:
>> break;
>
> I've applied the non-whitespace damaged patch (attached) but
> unfortunately I still see the "!TC on DATA XFER" bug with my NetBSD 5
> ISO under qemu-system-sparc :/ Note that the second part of the patch
> showed some fuzz so I'm wondering if this patch is complete or whether
> part of it is still missing?
>
> Also ESP patches should have an esp or scsi/esp prefix in the subject
> line and should CC the current SCSI maintainer (see MAINTAINERS file)
> which is currently Paolo.

Hi Olivier,

I've done some more testing on this patch today, and what I've found is 
that there are 2 types of error emitted from the NetBSD ESP driver: the 
majority of the "!TC on DATA XFER" messages go away under NetBSD 6 with 
the patch, but I still get the occasional one on the console, 
particularly with NetBSD 5. There are still messages about DMA 
interrupts appearing as can be seen at 
http://www.ilande.co.uk/tmp/netbsd5-esp.png.

Both Linux and NetBSD seem to install fine with the patch applied, so no 
regressions there - I haven't had a chance to test Solaris yet. If 
Artyom could give this a quick test on his collection of Solaris images 
then I'd say the patch is okay to apply.

More interesting is that with or without the patch, if you boot a 
standard Debian etch .qcow2 HD image and then shut it down then you get 
the following kernel panic: http://www.ilande.co.uk/tmp/debian-esp.png.

So my current conclusion is that this patch doesn't appear to cause any 
noticeable regressions outside of Solaris, however there is a still a 
problem somewhere with the ESP DMA interrupts on SPARC32.


ATB,

Mark.

      parent reply	other threads:[~2014-02-23 16:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-16 23:13 [Qemu-devel] [PATCH] Sun4m : SCSI ESP controller Olivier Danet
2014-02-20  8:58 ` Mark Cave-Ayland
2014-02-20 11:13   ` Paolo Bonzini
2014-02-23 17:25     ` Mark Cave-Ayland
2014-02-21 22:03   ` Olivier Danet
2014-02-23 16:50   ` Mark Cave-Ayland [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=530A26DF.8030900@ilande.co.uk \
    --to=mark.cave-ayland@ilande.co.uk \
    --cc=atar4qemu@gmail.com \
    --cc=blauwirbel@gmail.com \
    --cc=odanet@caramail.com \
    --cc=qemu-devel@nongnu.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).