Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp6457128imu; Wed, 30 Jan 2019 15:17:07 -0800 (PST) X-Google-Smtp-Source: ALg8bN4JdVaK2yjgJnk0yveapKkn5VDR333jNd3r7JD1lRl3Q3ANn4hyTafVMWdrzNZz4noqVayH X-Received: by 2002:a17:902:442:: with SMTP id 60mr30694460ple.73.1548890227812; Wed, 30 Jan 2019 15:17:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548890227; cv=none; d=google.com; s=arc-20160816; b=i8Lw1Aow2W9Hz0uquf+oqSNtVnpfhTVpiDZLPK94F6FeFekZOotevJry2lMDWpQ4HP 17HCeA7LRUCG+dPrFqDoBavfa4FcA1NPA1Jv5kRN6noDa4o4o5KqKFuouUEkI5s2Tcld NNvN+Bfr/OphJxj8lmVs/49uP0Mdinyr3g3oKNf9l5cxqoWu9VyAL+bg13zZNNrXasXY K+cOKACYK7jEea8vn/dG4KTgTzixZHFgpPLblyB9sTses/aQdhOpSuaq6/+F7wD/TV5c upoUocBckEXdX+ynAXvyK72JS+gJsJ5ExWpf5Uwqteq61DeV7kTn+7U+j0MA0iSvOn9o 8Smg== 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=otmj9UCNG3d9ttCOYHp0r+AU7FMpWAboxMgOujGU8ns=; b=taSBnrdosJg/0+BRed+SjjMlyoOcLU2CWfMmXJ6R2ex59x3ILQwDLfzka6kwcSW8rG PhJgE+v/E45RsrvcaNNAoKsvYMCYfJ1L2gDROoH0Lr/2+RZSC5DJ3QckdEMahR0ipxl0 Wuvj1Hp92GpKeo5IEIwqbxzr+AtPbmQYnstxD5DTbqijE4ZqUBPTLDHgHljXHaxi43XP A+dQQ9TF800YJL61x785z+IXGY6cgg6Ho4Tq1cTADEgkjWkSPT/MsKvjIGCva5d8B/KU jKGupIVK7Zb99PKsv+pAI1rS7pZ7advDGeu1DDuWzqNugdriRy8ia8ODNXsL+9QmrRHk Hmaw== 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 l14si2707257pgi.147.2019.01.30.15.16.52; Wed, 30 Jan 2019 15:17:07 -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 S1728522AbfA3XQn (ORCPT + 99 others); Wed, 30 Jan 2019 18:16:43 -0500 Received: from mx1.redhat.com ([209.132.183.28]:43372 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726799AbfA3XQm (ORCPT ); Wed, 30 Jan 2019 18:16:42 -0500 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 83E96C065F63; Wed, 30 Jan 2019 21:59:18 +0000 (UTC) Received: from redhat.com (ovpn-122-6.rdu2.redhat.com [10.10.122.6]) by smtp.corp.redhat.com (Postfix) with SMTP id 38F734115; Wed, 30 Jan 2019 21:59:16 +0000 (UTC) Date: Wed, 30 Jan 2019 16:59:14 -0500 From: "Michael S. Tsirkin" To: Konrad Rzeszutek Wilk Cc: Joerg Roedel , Jason Wang , 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, Thomas.Lendacky@amd.com Subject: Re: [PATCH 0/5 v5] Fix virtio-blk issue with SWIOTLB Message-ID: <20190130165754-mutt-send-email-mst@kernel.org> References: <20190130164007.26497-1-joro@8bytes.org> <20190130183513.GB27284@char.us.oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190130183513.GB27284@char.us.oracle.com> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Wed, 30 Jan 2019 21:59:18 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 30, 2019 at 01:35:13PM -0500, Konrad Rzeszutek Wilk wrote: > On Wed, Jan 30, 2019 at 05:40:02PM +0100, Joerg Roedel wrote: > > Hi, > > > > here is the next 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/ > > > > V3: https://lore.kernel.org/lkml/20190123163049.24863-1-joro@8bytes.org/ > > > > V4: https://lore.kernel.org/lkml/20190129084342.26030-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. > > > > Changes to v4 are: > > > > - Added Reviewed-by tags from Christoph > > > > - Added missing EXPORT_SYMBOL(_GPL) lines > > > > Please review. > > I can put it in my tree and send it to Linus .. unless folks want > to do it through a different tree? I queued it in my tree as it seems virtio specific. > > > > > 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 > > > > Documentation/DMA-API.txt | 8 ++++++++ > > drivers/block/virtio_blk.c | 10 ++++++---- > > drivers/virtio/virtio_ring.c | 11 +++++++++++ > > include/linux/dma-mapping.h | 16 ++++++++++++++++ > > include/linux/swiotlb.h | 11 +++++++++++ > > include/linux/virtio.h | 2 ++ > > kernel/dma/direct.c | 12 ++++++++++++ > > kernel/dma/swiotlb.c | 14 ++++++++++++++ > > 8 files changed, 80 insertions(+), 4 deletions(-) > > > > -- > > 2.17.1 > >