Received: by 10.223.164.202 with SMTP id h10csp1156382wrb; Fri, 17 Nov 2017 15:04:49 -0800 (PST) X-Google-Smtp-Source: AGs4zMaWEXKMOxsfeSXxhq1gtWgUKKwWJQrAorzsWCLIkDtwwB78+Q0pltvhoE9x/PPM/hkwqF6j X-Received: by 10.98.153.74 with SMTP id d71mr3599789pfe.145.1510959889022; Fri, 17 Nov 2017 15:04:49 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510959888; cv=none; d=google.com; s=arc-20160816; b=rNewXw1lGCzEUiPUN8ocs2VPuAfcB+MnVQ+5FG7wGUGvRlzDlq8fNxF8iBm9tg1N5P jKDzO060/c1r3njiJvo6FJUdRZ+fpyJKegqiIG2khKp2FJJE1NEnNwY7iytrQLRZwPW0 rr8KvE+ncFMW27NEUZ8I+DzHOl2sbqZIZ0LS/J+x27qbMHcfwO/S2138wKbstx6r6/d8 aZ+n8XpY1za/r4fU1oOBpTvElnXL5FHyvQJddubOelC8e4X1c09mxcQM6mgL8+dxfA9E ue5WLzH8tf1ubLY1NZ5xgOLb1Xm1cA0CfsaCI8Awn9OQ74fO2THHpJcQSSHLA74Rnyrx SlZg== 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=GTfFmn8phwknlh28zxcwzsw41R2YAcOMEGAmXqme0L4=; b=1IMewqvtCONdq+6KxalLtIhHOaWA5ss0SJQG9ZUJnrg80vLu6g8Wg6oHFJCqkKi8F9 3wgSk9tcS/+IaiHa1WVS14JOlR/fl0FVIc8Ur0wR8VeaYo16kExEENo7zYwJ0iZWxNYX w/1jInPMEnffWNIgUGLr9mH6Rfi5l0v4qiJaEmmr0qM9eCKqo0QMLlqLpcgkciMIP8wy 4OcJw//p+Msoll7yjEeKGJCQSw84VjT2KumaFkwlEjW2GXeB5RUCrnH0xKNHppisPCxH +PpWeiefUgD9cSMrCRJ3206ea7M5kgMqMLfxIa3AgQia/IWSCGgnNm4WIAn4dybnGdoS J+HA== 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 r59si3532687plb.10.2017.11.17.15.04.35; Fri, 17 Nov 2017 15:04:48 -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 S965461AbdKQQ01 (ORCPT + 93 others); Fri, 17 Nov 2017 11:26:27 -0500 Received: from mga02.intel.com ([134.134.136.20]:57047 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965345AbdKQQ0V (ORCPT ); Fri, 17 Nov 2017 11:26:21 -0500 Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Nov 2017 08:26:20 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,410,1505804400"; d="scan'208";a="6162888" Received: from otc-nc-03.jf.intel.com (HELO otc-nc-03) ([10.54.39.38]) by orsmga001.jf.intel.com with ESMTP; 17 Nov 2017 08:26:20 -0800 Date: Fri, 17 Nov 2017 07:48:34 -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 Subject: Re: [PATCH] iommu/vt-d: Fix scatterlist offset handling Message-ID: <20171117154833.GA56337@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> <20171116210933.GA53016@otc-nc-03> <20171117091814.6673aecf@t450s.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171117091814.6673aecf@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 Fri, Nov 17, 2017 at 09:18:14AM -0700, Alex Williamson wrote: > On Thu, 16 Nov 2017 13:09:33 -0800 > "Raj, Ashok" wrote: > > > > > > > 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. > > Ok. Who wants to toss in review and testing sign-offs? Clearly > there's been a lot more eyes and effort on this patch than reflected in > the original posting. I'll add a stable cc. Thanks, Reported by: Harsh Reviewed by: Ashok Raj Tested by: Jacob Pan > > Alex From 1584348169955377162@xxx Fri Nov 17 20:55:57 +0000 2017 X-GM-THRID: 1579793157804914964 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread