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 12864C77B7A for ; Tue, 16 May 2023 04:07:46 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229808AbjEPEHp (ORCPT ); Tue, 16 May 2023 00:07:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55006 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229719AbjEPEHn (ORCPT ); Tue, 16 May 2023 00:07:43 -0400 Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 531C7E2; Mon, 15 May 2023 21:07:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1684210062; x=1715746062; h=message-id:date:mime-version:cc:subject:to:references: from:in-reply-to:content-transfer-encoding; bh=YziHanXZZgtVTeTDOEw80tR1iSfnjM4PSBzGx7IvwG8=; b=IAa/7aDjwKKijbiMrzYOZj7EDgG1v2IVbs4kYdvSGrDQhU6t+dcv2Seb PuJstTZJK/DAajNG2BjQc/hGOLgQE2X94pHvw4gOzBdXjTPZ7jH2EFsSu QN9x8NQLkTb4rcUvwafrLTjXn5ITm8UtawMaBvAKdIYF8geOF/UQqdLpH WYeBETcPEw+rJwPJjIqbydE0DSWQ1EqHicMt0VeG6CF5YeNmDano+9yJh 5Qy8sGcp5jqe9XS4sU2W88vK14tcqF9MO/G2ExZtW7hp90ifjWZ66xxsT av/0sONBpO+jIzwV6XzGPSZPjUG2yDkNdlqsy7K58mVz/aAmL6UwqCD3A A==; X-IronPort-AV: E=McAfee;i="6600,9927,10711"; a="350210793" X-IronPort-AV: E=Sophos;i="5.99,277,1677571200"; d="scan'208";a="350210793" Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 May 2023 21:07:41 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10711"; a="704237247" X-IronPort-AV: E=Sophos;i="5.99,277,1677571200"; d="scan'208";a="704237247" Received: from allen-box.sh.intel.com (HELO [10.239.159.127]) ([10.239.159.127]) by fmsmga007.fm.intel.com with ESMTP; 15 May 2023 21:07:39 -0700 Message-ID: <2944e798-1599-df10-398f-1afa6e983bf2@linux.intel.com> Date: Tue, 16 May 2023 12:07:03 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Cc: baolu.lu@linux.intel.com, Kevin Tian , kvm@vger.kernel.org, Lixiao Yang , Matthew Rosato , Nicolin Chen , Yi Liu Subject: Re: [PATCH v7 01/19] iommufd: Move isolated msi enforcement to iommufd_device_bind() Content-Language: en-US To: Jason Gunthorpe , iommu@lists.linux.dev, linux-kselftest@vger.kernel.org References: <1-v7-6c0fd698eda2+5e3-iommufd_alloc_jgg@nvidia.com> From: Baolu Lu In-Reply-To: <1-v7-6c0fd698eda2+5e3-iommufd_alloc_jgg@nvidia.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On 5/15/23 10:00 PM, Jason Gunthorpe wrote: > With the recent rework this no longer needs to be done at domain > attachment time, we know if the device is usable by iommufd when we bind > it. > > The value of msi_device_has_isolated_msi() is not allowed to change while > a driver is bound. > > Reviewed-by: Kevin Tian > Signed-off-by: Jason Gunthorpe Reviewed-by: Lu Baolu Best regards, baolu