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

On 11/10/2014 07:32 PM, Paolo Bonzini wrote:
> 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?
> 
It's a complex thing. The documentation says 'ESP_TCHI returns the chip
id until been written to'.
And ESP_TCHI is strictly speaking only valid if the 'Features enabled'
bit is set in ESP_CFG2. (Not that the driver checks this).
To handle it correctly we would need to add a flag whenever ESP_TCHI
is written to, but I thought it'd be slightly too much.
Plus we're reloading the ESP_TCHI register anyway whenever a transfer
is started.

> Can you explain exactly what sequence of register reads/writes leads to
> the bug?
> 
CMD RST
DMA CMD NOP
-> ESP_TCHI should contain chip_id, but doesn't.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)

  reply	other threads:[~2014-11-10 20:11 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
2014-11-10 20:11   ` Hannes Reinecke [this message]
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=54611BD9.6020105@suse.de \
    --to=hare@suse.de \
    --cc=pbonzini@redhat.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).