qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Hannes Reinecke <hare@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCHv2] esp: Do not overwrite ESP_TCHI after reset
Date: Mon, 10 Nov 2014 19:32:19 +0100	[thread overview]
Message-ID: <546104B3.6020707@redhat.com> (raw)
In-Reply-To: <1415634775-4288-1-git-send-email-hare@suse.de>

On 10/11/2014 16:52, Hannes Reinecke wrote:
> After a reset ESP_TCHI should contain the unique ID
> of the chip. This value will be overwritten with the
> current tranfer count if the transfer count has
> previously been set.
> So we should always return the chip id if ESP_TCHI
> has never been written to.

What if ESP_TCHI was written 0?  Why should it return the chip id?

Can you explain exactly what sequence of register reads/writes leads to
the bug?

Paolo

> Signed-off-by: Hannes Reinecke <hare@suse.de>
> ---
>  hw/scsi/esp.c | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/hw/scsi/esp.c b/hw/scsi/esp.c
> index 5ab44d8..2caac1c 100644
> --- a/hw/scsi/esp.c
> +++ b/hw/scsi/esp.c
> @@ -364,7 +364,6 @@ void esp_hard_reset(ESPState *s)
>  {
>      memset(s->rregs, 0, ESP_REGS);
>      memset(s->wregs, 0, ESP_REGS);
> -    s->rregs[ESP_TCHI] = s->chip_id;
>      s->ti_size = 0;
>      s->ti_rptr = 0;
>      s->ti_wptr = 0;
> @@ -422,6 +421,11 @@ uint64_t esp_reg_read(ESPState *s, uint32_t saddr)
>          esp_lower_irq(s);
>  
>          return old_val;
> +    case ESP_TCHI:
> +        /* Return the unique id if the value has never been written */
> +        if (!s->wregs[ESP_TCHI]) {
> +            return s->chip_id;
> +        }
>      default:
>          break;
>      }
> 

  reply	other threads:[~2014-11-10 18:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10 15:52 [Qemu-devel] [PATCHv2] esp: Do not overwrite ESP_TCHI after reset Hannes Reinecke
2014-11-10 18:32 ` Paolo Bonzini [this message]
2014-11-10 20:11   ` Hannes Reinecke
2014-11-11 12:37     ` Paolo Bonzini
2014-11-11 12:43       ` Hannes Reinecke

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=546104B3.6020707@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=hare@suse.de \
    --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).