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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 69C49EE57DF for ; Wed, 13 Sep 2023 02:28:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237972AbjIMC21 (ORCPT ); Tue, 12 Sep 2023 22:28:27 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35652 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229719AbjIMC2Z (ORCPT ); Tue, 12 Sep 2023 22:28:25 -0400 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.120]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5B7BB1713 for ; Tue, 12 Sep 2023 19:28:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1694572101; x=1726108101; h=message-id:date:mime-version:cc:subject:to:references: from:in-reply-to:content-transfer-encoding; bh=ADJXPAGxhH/KIzMbrba+LZ+A/B+nI3RN78Cnn9H+UvU=; b=HlGVOA8HzfXnnFEFccthZd8uVd8ho4rzUs6Wl5BeB+RyBP85nT1lQaNL OElLuMupR9LRM6FB9JCG0WtnK82ECXo6HRyMBRP31liFjVEFZ8DYL2YtN k6YwtAeygbjh4KKGXb6rsxA5XGzyev3+HycUJ5e0n9U/6ozBgQgLxY/Xi 37Umx9D9H/Vs4o8TPcmWD9sTE6B4G7FgXPwra+tsjW+JVZTyo8R1LaLI5 aPXeExOur/4FPyFgIPB9wmfD+vZpBHKgnHrh8PqbIBYlIY8xlXoaA/3Tu Z9SSWgNt8TKwFXjH2Vw/aUHKnHSCRu1R4BeX8e5rl09f3xLDv7zTBDZma A==; X-IronPort-AV: E=McAfee;i="6600,9927,10831"; a="377454858" X-IronPort-AV: E=Sophos;i="6.02,142,1688454000"; d="scan'208";a="377454858" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 12 Sep 2023 19:28:20 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10831"; a="693689531" X-IronPort-AV: E=Sophos;i="6.02,142,1688454000"; d="scan'208";a="693689531" Received: from allen-box.sh.intel.com (HELO [10.239.159.127]) ([10.239.159.127]) by orsmga003.jf.intel.com with ESMTP; 12 Sep 2023 19:28:17 -0700 Message-ID: <0f4fb712-28e3-8620-6a65-59c9b9d77740@linux.intel.com> Date: Wed, 13 Sep 2023 10:25:16 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Cc: baolu.lu@linux.intel.com, Michael Shavit , Vasant Hegde , iommu@lists.linux.dev, linux-kernel@vger.kernel.org Subject: Re: [PATCH v4 2/6] iommu/vt-d: Remove mm->pasid in intel_sva_bind_mm() Content-Language: en-US To: Tina Zhang , Jason Gunthorpe , Kevin Tian References: <20230912125936.722348-1-tina.zhang@intel.com> <20230912125936.722348-3-tina.zhang@intel.com> From: Baolu Lu In-Reply-To: <20230912125936.722348-3-tina.zhang@intel.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 9/12/23 8:59 PM, Tina Zhang wrote: > The pasid is passed in as a parameter through .set_dev_pasid() callback. > Thus, intel_sva_bind_mm() can directly use it instead of retrieving the > pasid value from mm->pasid. > > Suggested-by: Lu Baolu > Signed-off-by: Tina Zhang > --- > drivers/iommu/intel/svm.c | 14 +++++++------- > 1 file changed, 7 insertions(+), 7 deletions(-) The intel_svm_bind_mm() could be further merged into intel_svm_set_dev_pasid(). It's fine if you keep it as is since we need more cleanup and refactoring work after this series get merged. So, Reviewed-by: Lu Baolu Best regards, baolu