Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp4661681ybp; Mon, 7 Oct 2019 11:48:34 -0700 (PDT) X-Google-Smtp-Source: APXvYqzfJIycey6OGipNI7goGW1xRCULFxUnLkxwJQNrEkKyRuHNhvn/rqi9EnvSIM62O3+Cl2T0 X-Received: by 2002:a17:906:1c5b:: with SMTP id l27mr25671830ejg.27.1570474114102; Mon, 07 Oct 2019 11:48:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570474114; cv=none; d=google.com; s=arc-20160816; b=ryy+ip7tRL+18ngzJ0EZ0qxwksFtHbBv1OGloBCxqUF387rYktwZpcS+YtpmX0xuQS g5+2HC8oa6acm3CI3KDrbw0/HAreaGkCCzrfHmm7Iwd/C1+01kpAtRUXtvOdUihQ3G+X OrfMx3sA3np2O9iv3IiR1S1awsW4sLURjcDiraiBo/kaeLwA0Z7kV7e0IEXUnKLQQHDL BgN4g0sWpz3ptkNjnDinZ9mY2L+UtrLFUTW3InYaU/vJbwbn5aBRsWs2hNLk3wJqIn9h e2DIyZ2ZCnYIdKyERvBjLKNLL3pWToroBTCbQNGaPoj3AGMor8ENDXBP7C5aR5nI59TC 8sNw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=FvHCXF6UssoJbnG00fU9ca600ax1byOS1Av/BpYNf+M=; b=m+qDmhUnlFPLPkzQzL8iZ81fpskXI3bhHkTG6IyoAEYT31rEcQSF1lmH0nPAWevleR 6XcvutNkhryVLTOqiz6TmPgfFKyn7j4fAN6944OUF5Gb7NFFFgiau64HWmZ4mQ0HGpfC m5SqWnL3XhOGDOOPxq/qvp3WGmrcosoAh/dB3tPpt0wb9xkPEQ4hrmHNBAYEXi4iFO3g PckCEMVHD/yx22T6weyijwbBCEZ89Ab2GPxGupQTcsAgFf8tK6M2G6j1Mk0V9cuc4rQG fwo2dNmpVNnYaKg54vAkIIBHZZHta6Q0EX/Ldpgv7xw9ilk5E0YcGZ15RYHCB7NGDUT3 PLrQ== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id se14si7535140ejb.322.2019.10.07.11.48.10; Mon, 07 Oct 2019 11:48:34 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728325AbfJGSr5 (ORCPT + 99 others); Mon, 7 Oct 2019 14:47:57 -0400 Received: from verein.lst.de ([213.95.11.211]:40176 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728079AbfJGSr4 (ORCPT ); Mon, 7 Oct 2019 14:47:56 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id 6422568B20; Mon, 7 Oct 2019 20:47:54 +0200 (CEST) Date: Mon, 7 Oct 2019 20:47:54 +0200 From: Christoph Hellwig To: Arvind Sankar Cc: Christoph Hellwig , Christoph Hellwig , linux-kernel@vger.kernel.org Subject: Re: ehci-pci breakage with dma-mapping changes in 5.4-rc2 Message-ID: <20191007184754.GB31345@lst.de> References: <20191007022454.GA5270@rani.riverdale.lan> <20191007073448.GA882@lst.de> <20191007175430.GA32537@rani.riverdale.lan> <20191007175528.GA21857@lst.de> <20191007175630.GA28861@infradead.org> <20191007175856.GA42018@rani.riverdale.lan> <20191007183206.GA13589@rani.riverdale.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191007183206.GA13589@rani.riverdale.lan> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 07, 2019 at 02:32:07PM -0400, Arvind Sankar wrote: > On Mon, Oct 07, 2019 at 01:58:57PM -0400, Arvind Sankar wrote: > > On Mon, Oct 07, 2019 at 10:56:30AM -0700, Christoph Hellwig wrote: > > > On Mon, Oct 07, 2019 at 07:55:28PM +0200, Christoph Hellwig wrote: > > > > On Mon, Oct 07, 2019 at 01:54:32PM -0400, Arvind Sankar wrote: > > > > > It doesn't boot with the patch. Won't it go > > > > > dma_get_required_mask > > > > > -> intel_get_required_mask > > > > > -> iommu_need_mapping > > > > > -> dma_get_required_mask > > > > > ? > > > > > > > > > > Should the call to dma_get_required_mask in iommu_need_mapping be > > > > > replaced with dma_direct_get_required_mask on top of your patch? > > > > > > > > Yes, sorry. > > > > > > Actually my patch already calls dma_direct_get_required_mask. > > > How did you get the loop? > > > > The function iommu_need_mapping (not changed by your patch) calls > > dma_get_required_mask internally, to check whether the device's dma_mask > > is big enough or not. That's the call I was asking whether it needs to > > be changed. > > Yeah the attached patch seems to fix it. That looks fine to me: Acked-by: Christoph Hellwig