Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp891969imm; Tue, 5 Jun 2018 06:11:27 -0700 (PDT) X-Google-Smtp-Source: ADUXVKJETfPgqNTziY7q6TOXqYR1jyN4u+MeFEKk+qt88JhSUFh4RzWh8Ow+InPZdhm4HEeaK0df X-Received: by 2002:a63:730d:: with SMTP id o13-v6mr4346309pgc.1.1528204287682; Tue, 05 Jun 2018 06:11:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528204287; cv=none; d=google.com; s=arc-20160816; b=m+P9bngbichzKhSyigA6dopNYSusFM/6uOuC6Fs1z3rwgEMiKEHAXxbU+3ZXp5OXR9 2NxdkolEUCD80K4Pb+u6vnNqboZG9qGmS6E2N+P8cfZ51NZhXEPlSjvIhGCreYPiuzmb LS/kUet2fH/1vNvGbzSF0ggvgE1g4bbbNkxQYKjsGuF/V0RWlK9iwtZSOgZ3l4yY5hLl bNYp4IFtCf0QTH1BryU8OCjoVZnGvIxyh1i4yzqGk7yLWa+aVI4SHVNnvHP8F8SZ3urP HOAklRuVEUNKqm1fAAyyZqR1o9s8gNdIv+915E6hQacm5/RYfgi+iznkwrSl6iyA+k89 9jxg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :from:references:cc:to:subject:reply-to:arc-authentication-results; bh=2nGf1iHsm8U9oQ2+cQtzg9t2gMf59Q78EZ97mt8uutU=; b=CUGynZxHWStoVo7pvGKRQauguzYUr3UyhP7pKr15Z0hmAsnjBZAt4bZz55io84LlH4 eH3rZjKDNkC98B51VYPpIfrPqDaU1QH2Ay1MYicC7bypEvyWFGCB/G757WVgn4mRgMjg 4f/YI0pKf151gVasr2xpdfi6GI3gAJYpcjTfwngzlgYhpihRi+M/gcQf5eDg/w3k0VeG vVijCe/0G5k0u4xmtOMMSQIzHd54mw5tBXOR8h1wcPwWq/WUBu7T/fiDuRKcHaulkHnA 2S7+i1fCopjVHNcfD6o6JFv1lMWAhHcQrlhoTUjetBhCSYVpihKBJo9+XfqoS6bF2anl sBdA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b60-v6si49197098plc.270.2018.06.05.06.11.13; Tue, 05 Jun 2018 06:11:27 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751908AbeFENKn (ORCPT + 99 others); Tue, 5 Jun 2018 09:10:43 -0400 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:54738 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751732AbeFENKm (ORCPT ); Tue, 5 Jun 2018 09:10:42 -0400 Received: from pps.filterd (m0098409.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w55CwwPJ014284 for ; Tue, 5 Jun 2018 09:10:41 -0400 Received: from e06smtp02.uk.ibm.com (e06smtp02.uk.ibm.com [195.75.94.98]) by mx0a-001b2d01.pphosted.com with ESMTP id 2jdr3hgt0w-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 05 Jun 2018 09:10:37 -0400 Received: from localhost by e06smtp02.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 5 Jun 2018 14:10:15 +0100 Received: from b06cxnps3075.portsmouth.uk.ibm.com (9.149.109.195) by e06smtp02.uk.ibm.com (192.168.101.132) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Tue, 5 Jun 2018 14:10:13 +0100 Received: from d06av21.portsmouth.uk.ibm.com (d06av21.portsmouth.uk.ibm.com [9.149.105.232]) by b06cxnps3075.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id w55DACSW16646190 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Tue, 5 Jun 2018 13:10:12 GMT Received: from d06av21.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 387C65203F; Tue, 5 Jun 2018 12:59:52 +0100 (BST) Received: from [9.152.224.33] (unknown [9.152.224.33]) by d06av21.portsmouth.uk.ibm.com (Postfix) with ESMTP id EEFAF5204B; Tue, 5 Jun 2018 12:59:51 +0100 (BST) Reply-To: pmorel@linux.ibm.com Subject: Re: [PATCH v2 06/10] vfio: ccw: Make FSM functions atomic To: Cornelia Huck , Pierre Morel Cc: pasic@linux.vnet.ibm.com, bjsdjshi@linux.vnet.ibm.com, linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org References: <1527243678-3140-1-git-send-email-pmorel@linux.vnet.ibm.com> <1527243678-3140-7-git-send-email-pmorel@linux.vnet.ibm.com> <20180605133850.3509a3d3.cohuck@redhat.com> From: Pierre Morel Date: Tue, 5 Jun 2018 15:10:11 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180605133850.3509a3d3.cohuck@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-TM-AS-GCONF: 00 x-cbid: 18060513-0008-0000-0000-000002445EFE X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18060513-0009-0000-0000-000021AA644D Message-Id: <46613ac7-3156-7a78-7d49-acbc3f615b76@linux.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-06-05_05:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1805220000 definitions=main-1806050151 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/06/2018 13:38, Cornelia Huck wrote: > On Fri, 25 May 2018 12:21:14 +0200 > Pierre Morel wrote: > >> We use mutex around the FSM function call to make the FSM >> event handling and state change atomic. > I'm still not really clear as to what this mutex is supposed to > serialize: > > - Modification of the state? > - Any calls in the state machine? > - A combination? (That would imply that we only deal with the state in > the state machine.) yes to all > >> Signed-off-by: Pierre Morel >> --- >> drivers/s390/cio/vfio_ccw_drv.c | 3 +-- >> drivers/s390/cio/vfio_ccw_private.h | 3 +++ >> 2 files changed, 4 insertions(+), 2 deletions(-) >> >> diff --git a/drivers/s390/cio/vfio_ccw_drv.c b/drivers/s390/cio/vfio_ccw_drv.c >> index 6b7112e..98951d5 100644 >> --- a/drivers/s390/cio/vfio_ccw_drv.c >> +++ b/drivers/s390/cio/vfio_ccw_drv.c >> @@ -73,8 +73,6 @@ static void vfio_ccw_sch_io_todo(struct work_struct *work) >> >> private = container_of(work, struct vfio_ccw_private, io_work); >> vfio_ccw_fsm_event(private, VFIO_CCW_EVENT_INTERRUPT); >> - if (private->mdev) >> - private->state = VFIO_CCW_STATE_IDLE; > Looks like an unrelated change? If you want to do all state changes > under the mutex, that should rather be moved than deleted, shouldn't it? It is moved to fsm_irq() which is called under mutex. fsm_irq() returns VFIO_CCW_STATE_IDLE. > >> } >> >> static void vfio_ccw_sch_event_todo(struct work_struct *work) -- Pierre Morel Linux/KVM/QEMU in Böblingen - Germany