From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AC9DCC46477 for ; Tue, 18 Jun 2019 15:28:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 7A09120B1F for ; Tue, 18 Jun 2019 15:28:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1560871718; bh=cBZbIGQ+cjyD2YCVRDOXcoe7z6QzrPpzbzN0znS/Ylg=; h=Subject:To:Cc:References:From:Date:In-Reply-To:List-ID:From; b=Rf+8WkBZbmz6IpZCer7cxXcA87LemaxlwZ9li91VfzJeIqxB2boVmg3dIhJXFpdCe N2h+I/ar3IAIMs9sr7jq+KyGFzGr7wIWlIMnWRRtw9MoRjd2FWfF7S08tQgh28jyG5 jps6dn1zwgHBhGk5qNEauZCnynmu+jKpJikruUBE= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729412AbfFRP2h (ORCPT ); Tue, 18 Jun 2019 11:28:37 -0400 Received: from mail.kernel.org ([198.145.29.99]:55228 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729247AbfFRP2h (ORCPT ); Tue, 18 Jun 2019 11:28:37 -0400 Received: from [192.168.1.112] (c-24-9-64-241.hsd1.co.comcast.net [24.9.64.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 031B92085A; Tue, 18 Jun 2019 15:28:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1560871716; bh=cBZbIGQ+cjyD2YCVRDOXcoe7z6QzrPpzbzN0znS/Ylg=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=1637osodxbXA+dd8NcCz7z4PZoJd2L4ooz5xgXaHLyVoXzk6mzzxCFsnF70fvSYaj rxwiYsehj0Nwqj96sUhbw7/ewZ6peonITYgoV53cZ0Lc/Fz3dnxXt5nuaECF1D648A wRwkpNFXQQ0FTiqYqUEkbxk32ximtj+bSI7AepPk= Subject: Re: How to resolve an issue in swiotlb environment? To: Alan Stern Cc: Christoph Hellwig , Valentina Manea , Oliver Neukum , "iommu@lists.linux-foundation.org" , Yoshihiro Shimoda , "linux-block@vger.kernel.org" , Linux-Renesas , "linux-usb@vger.kernel.org" , shuah References: From: shuah Message-ID: <20684ef6-7da7-90ed-4cd6-3bc46202de6d@kernel.org> Date: Tue, 18 Jun 2019 09:28:35 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-usb-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org On 6/14/19 8:44 AM, Alan Stern wrote: > On Thu, 13 Jun 2019, shuah wrote: > >>> Great! So all we have to do is fix vhci-hcd. Then we can remove all >>> the virt_boundary_mask stuff from usb-storage and uas entirely. >>> >>> (I'm assuming wireless USB isn't a genuine issue. As far as I know, it >>> is pretty much abandoned at this point.) >>> >>> Valentina and Shua: Adding SG support to vhci-hcd shouldn't be too >>> hard. It ought to be possible even without changing the network >>> protocol. >>> >> >> I will start taking a look at this. Is there a target release in plan >> to drop virt_boundary_mask stuff? > > Not yet. But since it doesn't do what we want anyway, this should be > fixed quickly. > Sounds good. I am working on it. thanks, -- Shuah