From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cornelia Huck Subject: Re: [PATCH 09/10] vfio: ccw: Suppressing the BOXED state Date: Wed, 25 Apr 2018 10:44:29 +0200 Message-ID: <20180425104429.582618f8.cohuck@redhat.com> References: <1524149293-12658-1-git-send-email-pmorel@linux.vnet.ibm.com> <1524149293-12658-10-git-send-email-pmorel@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1524149293-12658-10-git-send-email-pmorel@linux.vnet.ibm.com> Sender: linux-kernel-owner@vger.kernel.org List-Archive: List-Post: To: 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 List-ID: On Thu, 19 Apr 2018 16:48:12 +0200 Pierre Morel wrote: > VFIO_CCW_STATE_BOXED and VFIO_CCW_STATE_BUSY are the same > states. > Let's only keep one: VFIO_CCW_STATE_BUSY > > Signed-off-by: Pierre Morel > --- > drivers/s390/cio/vfio_ccw_fsm.c | 9 --------- > drivers/s390/cio/vfio_ccw_private.h | 1 - > 2 files changed, 10 deletions(-) I think they were initially supposed to cover two different things: - BUSY: we're currently dealing with an I/O request - BOXED: the device currently won't talk to us or we won't talk to it It seems we never really did anything useful with BOXED; but should we?