Received: by 10.192.165.148 with SMTP id m20csp552705imm; Wed, 25 Apr 2018 04:09:05 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+sP/NllolVCnmfeUv6SzezJwwgWaAjosBOrsJgNZTOCtgMUbhuQdazY79pq82W0dxRBXKE X-Received: by 10.101.88.194 with SMTP id e2mr23477692pgu.229.1524654545507; Wed, 25 Apr 2018 04:09:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524654545; cv=none; d=google.com; s=arc-20160816; b=gEMVd09A4XwXk0xN8nHfZgOLyxj1ZwCoL+ZipG1SaV3SHXVPtgfUK8xvPWJGLrpRce 4PDVa2VyL0BkqvvDqovCKTVvXTnPe4jEGXr8VDxvcxrEPrWpXuU0lEsS3EVBUAsz+BKg tgm8A9alZ4ghYIU0QGMrG/visfnW4VTd2hEv6x94itUMi9AJ3e1/mTF0XuCW68ig/4dh Vju6rqRzu55dSMQO/Go7krCi0PDY3PA0Au8RBJ/vaOl+QLHFH9pOtj1x/g6lBT4Mn+od /RLCuy+1HqM8LKfYD4qbaWG8BlLia5vM1lVQN8P56QpboYTXgjWnzQBmNINoBSq2Bp/Y pABA== 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-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date:from :references:cc:to:subject:arc-authentication-results; bh=G+rVhZKHKrh+1wVtenDGIRdOuySSeI42eiGkqYbzVBI=; b=znfHJlXvKEx4XeZBtul80LSp25f4iXcmL0TeQ6FD3zGJu+5XM6xUnXYUIiQ+5V99eA B10Ifx5RvXw0NmvbplYgeDj3sTVnwIkIqMHMVdIZIwEWITxt9lefmcwg7q7QaKA8sqRF owKawhocpw0UXNfSz1QbJmSZSI7M1J2Q1xYjOLqkwDyVWgHDiBCqDLLW5WN7Zvw8ogfP OST0Zl0TYXLlar21dVCMsh6q8EWBPuxpJmDh9ay3y8+QR9+T67eCCFmP5TjXZThHiiDR DPm5/DcwFj1qPryysR1Lgb/bu6sMdlGR2JdqtOaR+sWQr0D4+kUr5umgG9PCoP/89n6J RRsA== 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 w10si15005482pfi.88.2018.04.25.04.08.51; Wed, 25 Apr 2018 04:09:05 -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 S1754141AbeDYLGn (ORCPT + 99 others); Wed, 25 Apr 2018 07:06:43 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:46944 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752831AbeDYLGh (ORCPT ); Wed, 25 Apr 2018 07:06:37 -0400 Received: from pps.filterd (m0098420.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w3PB63dt021932 for ; Wed, 25 Apr 2018 07:06:36 -0400 Received: from e06smtp15.uk.ibm.com (e06smtp15.uk.ibm.com [195.75.94.111]) by mx0b-001b2d01.pphosted.com with ESMTP id 2hjnqj6ygs-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 25 Apr 2018 07:06:36 -0400 Received: from localhost by e06smtp15.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 25 Apr 2018 12:06:34 +0100 Received: from b06cxnps3075.portsmouth.uk.ibm.com (9.149.109.195) by e06smtp15.uk.ibm.com (192.168.101.145) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Wed, 25 Apr 2018 12:06:32 +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 w3PB6WuE2949620; Wed, 25 Apr 2018 11:06:32 GMT Received: from d06av21.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 3FDB652049; Wed, 25 Apr 2018 10:57:10 +0100 (BST) Received: from oc3836556865.ibm.com (unknown [9.152.104.203]) by d06av21.portsmouth.uk.ibm.com (Postfix) with ESMTP id C78945203F; Wed, 25 Apr 2018 10:57:09 +0100 (BST) Subject: Re: [PATCH 01/10] vfio: ccw: Moving state change out of IRQ context To: Cornelia Huck Cc: Pierre Morel , Dong Jia Shi , pasic@linux.vnet.ibm.com, linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org References: <1524149293-12658-1-git-send-email-pmorel@linux.vnet.ibm.com> <1524149293-12658-2-git-send-email-pmorel@linux.vnet.ibm.com> <20180424065442.GV12194@bjsdjshi@linux.vnet.ibm.com> <20180424115929.5b5e1ff0.cohuck@redhat.com> <245ee547-75bc-95f5-5acb-bfa96f91afd2@linux.ibm.com> <20180425085726.3a8a97a5.cohuck@redhat.com> From: Halil Pasic Date: Wed, 25 Apr 2018 13:06:31 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180425085726.3a8a97a5.cohuck@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 x-cbid: 18042511-0020-0000-0000-000004159FBF X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18042511-0021-0000-0000-000042AA0B2D Message-Id: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-04-25_03:,, 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 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000 definitions=main-1804250105 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/25/2018 08:57 AM, Cornelia Huck wrote: >> AFAIU this will be the problem of the person implementing the clear >> and the halt for vfio-ccw. I.e. it's a non-problem right now. > Well, that person is me:) I will post some RFC Real Soon Now if I stop > getting sidetracked... > Makes sense. It should be fine either way AFAIU. CSCH, more precisely the clear function is supposed to clear the interruption request(s) too. But I guess there is no way of the CP to identify an I/O interrupt that should have been cleared -- that is catch us disrespecting the architecture. I can't think of a way to establish must happen before relationship... But discarding the first interrupt and delivering just one for the CSCH is fine too for the same reason. Regards, Halil