Received: by 10.223.164.202 with SMTP id h10csp215716wrb; Thu, 16 Nov 2017 22:39:17 -0800 (PST) X-Google-Smtp-Source: AGs4zMbciescFU86AxMIX14N372JgoE/TQdQ/+W/G3GgigUxo8ThglZN0bWHRXGabgOsSKI/iMff X-Received: by 10.101.75.142 with SMTP id t14mr4161506pgq.122.1510900757576; Thu, 16 Nov 2017 22:39:17 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510900757; cv=none; d=google.com; s=arc-20160816; b=EN635INYPZLq5muNuAYqlHlSIh6LEmx5CdtyY0GMUKwK7F93rBKE3uc5opp2x5TNXx i3DbpUxaxdnMjVTxkyJGykltvrMeG+GIFI4Izy1nb8G8pwyGNh7oRnqDXMVTzwXZ+haz 4gboVb5ch3scGja4U0zi3OLzszaC4eodBE8zPVQKsoflnjZrypV1icixoeesSNF4BqzS w38OOq4246CYbsyJhXL+dReoXXW4RLMbYsX/bMdrfQtFj2WxHk/fceysbSb5riYUl8P4 GOj1U+8MWqQ6WWudvDaFJ6gu34/BN5qG1gVb+OVrRVEPK5gusHG5NeBWWJDFLh990U4i BZ1w== 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:arc-authentication-results; bh=ppR0eh9JuGvAbX8+ieN4VChWwAP8PQjTAeLN9vyFL50=; b=oDq21EGUbWLwGCHyEMwUtM524zg8taCutKOAJiZhn8BArlPgA7lHdIDueV9yY0iiB8 OhH4t1Nvdw0suMpwfI2MPkAHNCXA9M3aquLpH6s1xh2w7HPCKmQPFaio6T9bnSCUEXr/ PdI63kbI5LgLrhcgD5MMJt/C201gZiS+BbDXAaDYG92cTCe6RCNOehIviVOO2FryUIFf uUUCKbITSN1yMhPc9lhdWl+wD4wWoqZdW5t84+QJyKyD/mVXCHzYHSu34/7enIU8P+Bm arSQDplUGcDBoZZ0iy0h+8FIcDdEubSBmWVlDIQP3FtIlHnQi7LTz6kAEgWlLfyN791c 22Xg== 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 t15si2224085pgo.118.2017.11.16.22.39.04; Thu, 16 Nov 2017 22:39:17 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935831AbdKPVoq (ORCPT + 92 others); Thu, 16 Nov 2017 16:44:46 -0500 Received: from mga07.intel.com ([134.134.136.100]:38864 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933899AbdKPVok (ORCPT ); Thu, 16 Nov 2017 16:44:40 -0500 Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Nov 2017 13:44:39 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,405,1505804400"; d="scan'208";a="150264805" Received: from otc-nc-03.jf.intel.com (HELO otc-nc-03) ([10.54.39.38]) by orsmga004.jf.intel.com with ESMTP; 16 Nov 2017 13:44:39 -0800 Date: Thu, 16 Nov 2017 13:09:33 -0800 From: "Raj, Ashok" To: Alex Williamson Cc: Jacob Pan , leedom@chelsio.com, herbert@gondor.apana.org.au, David Woodhouse , linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org, linux-crypto@vger.kernel.org, Harsh@chelsio.com, Ashok Raj Subject: Re: [PATCH] iommu/vt-d: Fix scatterlist offset handling Message-ID: <20171116210933.GA53016@otc-nc-03> References: <644c3e01654f8bd48d669c36e424959d6ef0e27e.1506607370.git.robin.murphy@arm.com> <1507035334.29211.105.camel@infradead.org> <20171006144309.GA30803@8bytes.org> <20171106104709.06b38f7c@jacob-builder> <20171115155456.141a6dc8@jacob-builder> <20171116143244.2583d044@t450s.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171116143244.2583d044@t450s.home> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Alex On Thu, Nov 16, 2017 at 02:32:44PM -0700, Alex Williamson wrote: > On Wed, 15 Nov 2017 15:54:56 -0800 > Jacob Pan wrote: > > > Hi Alex and all, > > > > Just wondering if you could merge Robin's patch for the next rc. From > > all our testing, this seems to be a solid fix and should be included in > > the stable releases as well. > > Hi Jacob, > > Sorry, this wasn't on my radar, I only scanned for patches back through > about when Joerg refreshed his next branch (others on the list speak up > if I didn't pickup your patches for the v4.15 merge window). > > This patch makes sense to me and I'm glad you were able to work through > the anomaly Harsh saw in testing as an unrelated issue, but... > > > What do we do about this? I certainly can't rip out large page support > and put a stable tag on the patch. I'm not really spotting what's > wrong with large page support here, other than the comment about it > being a mess. Suggestions? Thanks, > Largepage seems to work and i don't think we need to rip it out. When Harsh tested it at one point we thought disabling super-page seemed to make the problem go away. Jacob tested and we still saw the need for Robin's patch. Yes, the function looks humongous but i don't think we should wait for that before this merge. Cheers, Ashok From 1584273787997254500@xxx Fri Nov 17 01:13:41 +0000 2017 X-GM-THRID: 1579793157804914964 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread