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: Tue, 11 Nov 2014 13:43:37 +0100 [thread overview]
Message-ID: <54620479.9060505@suse.de> (raw)
In-Reply-To: <546202FD.7060605@redhat.com>
On 11/11/2014 01:37 PM, Paolo Bonzini wrote:
>
>
> On 10/11/2014 21:11, Hannes Reinecke wrote:
>> 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.
>
> I'm worried that the chip_id will reappear if you write a low (<65536)
> value to ESP_TCLOW/MED/HI.
>
> Adding the flag is just a couple lines more than this patch, let's do it
> right.
>
Right.
Will be sending an updated patch.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 21284 (AG Nürnberg)
prev parent reply other threads:[~2014-11-11 12:43 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
2014-11-11 12:37 ` Paolo Bonzini
2014-11-11 12:43 ` Hannes Reinecke [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=54620479.9060505@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).