Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp1108147imu; Wed, 23 Jan 2019 10:53:10 -0800 (PST) X-Google-Smtp-Source: ALg8bN4R1U3IpqpWiV81SJgGpHw0EF1Hi4YuzbW0EDIT14TlT7LtywVmKp5keGFaNY2vEj63PP78 X-Received: by 2002:a17:902:887:: with SMTP id 7mr3394968pll.164.1548269590814; Wed, 23 Jan 2019 10:53:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548269590; cv=none; d=google.com; s=arc-20160816; b=NjlKUX7wNKBSKn9yK+JOEiS3E30SyKySmBl76RswtPBvhgONd+m96KKP+r9rzGpNda NcuTJe74TJitTO2hegLeAJp0fwHPBNcBDOQSKo539j6qeFH7PWbDgqufs+/zvdy7ZDV2 Pp6qQqui6+sMBBec5d89PWHSAQjCgLe+AEyjJwaRBlAYVFYPlsZDFPSupjeWfVPBAiDt JZ2A2NFfZgyNI45lkS4BsMi26e7dENS9oXm7tzp0MKsBKI/f8gSzm4JaT8DWf7uEQb4H fMTq0hxz3C9/zeQBm7kzbrv3lHOidcouuE+RT+c7AGULxwAAAmERbCnUzuaEsWuhI8+A XJHw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=bAOPYU1jU40ntMhAb+vJ3bSmRxhQI/2VD92h42NVCKM=; b=S/J1z20D2WVs19az1MjD37mJFsYcroETSq6YvVi4hoYIzu36dB+d2UVezjZYrSwtHE BkgxnBZwMCIJ4LbimXUp1EPjDtvXXjvUKR0RYAKmiJxeKaZtq9Doq9SVdi3PYkxr2Brf t17ujoRxDJwqV7gKMDd+APotT57DdNJss/LqBYJKdH6+uUw0f0C4UxSWSXjYP57lb87K kAnMmTmXKAH1CVnU0nHMa3TLitsHEZH4OBhmteLlXpxjlGfP8xWyQTVbNLwbq+4pcTL3 golquzzE3yvYO2ErjmmKWKA3+fgjkl/jIVJK5ZZfamLeHmJBJxf/nyl/l289+gaLbB2u cqTw== 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=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p19si3993314pgj.375.2019.01.23.10.52.55; Wed, 23 Jan 2019 10:53:10 -0800 (PST) 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=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726357AbfAWSvc (ORCPT + 99 others); Wed, 23 Jan 2019 13:51:32 -0500 Received: from mx1.redhat.com ([209.132.183.28]:52608 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725999AbfAWSvc (ORCPT ); Wed, 23 Jan 2019 13:51:32 -0500 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 018DBA429A; Wed, 23 Jan 2019 18:51:32 +0000 (UTC) Received: from redhat.com (ovpn-123-123.rdu2.redhat.com [10.10.123.123]) by smtp.corp.redhat.com (Postfix) with SMTP id 043915C23D; Wed, 23 Jan 2019 18:51:29 +0000 (UTC) Date: Wed, 23 Jan 2019 13:51:29 -0500 From: "Michael S. Tsirkin" To: Joerg Roedel Cc: Jason Wang , Konrad Rzeszutek Wilk , Christoph Hellwig , Jens Axboe , virtualization@lists.linux-foundation.org, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org, jfehlig@suse.com, jon.grimm@amd.com, brijesh.singh@amd.com, jroedel@suse.de Subject: Re: [PATCH 0/5 v3] Fix virtio-blk issue with SWIOTLB Message-ID: <20190123135000-mutt-send-email-mst@kernel.org> References: <20190123163049.24863-1-joro@8bytes.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190123163049.24863-1-joro@8bytes.org> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.28]); Wed, 23 Jan 2019 18:51:32 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 23, 2019 at 05:30:44PM +0100, Joerg Roedel wrote: > Hi, > > here is the third version of this patch-set. Previous > versions can be found here: > > V1: https://lore.kernel.org/lkml/20190110134433.15672-1-joro@8bytes.org/ > > V2: https://lore.kernel.org/lkml/20190115132257.6426-1-joro@8bytes.org/ > > The problem solved here is a limitation of the SWIOTLB implementation, > which does not support allocations larger than 256kb. When the > virtio-blk driver tries to read/write a block larger than that, the > allocation of the dma-handle fails and an IO error is reported. OK looks good to me. I will park this in my tree for now this way it will get testing in linux-next. Can I get an ack from DMA maintainers on the DMA bits for merging this in 5.0? > Changes to v2 are: > > * Check if SWIOTLB is active before returning its limit in > dma_direct_max_mapping_size() > > * Only apply the maximum segment limit in virtio-blk when > DMA-API is used for the vring > > Please review. > > Thanks, > > Joerg > > Joerg Roedel (5): > swiotlb: Introduce swiotlb_max_mapping_size() > swiotlb: Add is_swiotlb_active() function > dma: Introduce dma_max_mapping_size() > virtio: Introduce virtio_max_dma_size() > virtio-blk: Consider virtio_max_dma_size() for maximum segment size > > drivers/block/virtio_blk.c | 10 ++++++---- > drivers/virtio/virtio_ring.c | 10 ++++++++++ > include/linux/dma-mapping.h | 16 ++++++++++++++++ > include/linux/swiotlb.h | 11 +++++++++++ > include/linux/virtio.h | 2 ++ > kernel/dma/direct.c | 11 +++++++++++ > kernel/dma/swiotlb.c | 10 ++++++++++ > 7 files changed, 66 insertions(+), 4 deletions(-) > > -- > 2.17.1