From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:58106 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726660AbgENMIo (ORCPT ); Thu, 14 May 2020 08:08:44 -0400 Date: Thu, 14 May 2020 14:08:08 +0200 From: Cornelia Huck Subject: Re: [kvm-unit-tests PATCH v6 07/10] s390x: css: msch, enable test Message-ID: <20200514140808.269f6485.cohuck@redhat.com> In-Reply-To: References: <1587725152-25569-1-git-send-email-pmorel@linux.ibm.com> <1587725152-25569-8-git-send-email-pmorel@linux.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-s390-owner@vger.kernel.org List-ID: To: Pierre Morel Cc: Janosch Frank , kvm@vger.kernel.org, linux-s390@vger.kernel.org, david@redhat.com, thuth@redhat.com On Tue, 28 Apr 2020 10:27:36 +0200 Pierre Morel wrote: > On 2020-04-27 15:11, Janosch Frank wrote: > > On 4/24/20 12:45 PM, Pierre Morel wrote: > >> This is NOT a routine to really enable the channel, no retry is done, > >> in case of error, a report is made. > > > > Would we expect needing retries for the pong device? > > Yes it can be that we need to retry some instructions if we want them to > succeed. > This is the case for example if we develop a driver for an operating system. > When working with firmware, sometime, things do not work at the first > time. Mostly due to races in silicium, firmware or hypervisor or between > them all. > > Since our purpose is to detect such problems we do not retry > instructions but report the error. > > If we detect such problem we may in the future enhance the tests. I think I've seen retries needed on z/VM in the past; do you know if that still happens?