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 0E17AC4167B for ; Tue, 5 Dec 2023 01:18:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231618AbjLEBSa (ORCPT ); Mon, 4 Dec 2023 20:18:30 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39516 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229575AbjLEBS2 (ORCPT ); Mon, 4 Dec 2023 20:18:28 -0500 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.93]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5EEFCC9; Mon, 4 Dec 2023 17:18:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1701739115; x=1733275115; h=message-id:date:mime-version:cc:subject:to:references: from:in-reply-to:content-transfer-encoding; bh=ANNzQJqNaKlCYsNCLNZpFEjS7XvSSIJhQXWDN5zdWnU=; b=KgwornHghuqAnm+4GbkGOuSNQoO782OkqAnav3KrvGhjiKPpHwmKITtk ycH55oqNXrw/LTEmx8NGtb0dmWUh+1n8s9P498k2SBkm5269CBC8RppCb Hmmv60MmvKQWn1v9l2/r2uAxiKpYM6wPp/VtXL0IE3l4ETP9/yLCmqcNh m3A5f81+u042bb3vAbN68mgYOxPhX6ulxc4XkiiTzWB3sCLq13FpzUOL3 R+FmaKaudLn/OaD1Wd3Coirstf+nJafUZ04W3U5surFcdazEDalodBwMu Dl3YhPbepOu8uCImqZxE2CVLUvsif0ydRdDBT8RnN0j/aeRYIWSnHK28Q w==; X-IronPort-AV: E=McAfee;i="6600,9927,10914"; a="390975781" X-IronPort-AV: E=Sophos;i="6.04,251,1695711600"; d="scan'208";a="390975781" Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Dec 2023 17:18:35 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10914"; a="841254453" X-IronPort-AV: E=Sophos;i="6.04,251,1695711600"; d="scan'208";a="841254453" Received: from allen-box.sh.intel.com (HELO [10.239.159.127]) ([10.239.159.127]) by fmsmga004.fm.intel.com with ESMTP; 04 Dec 2023 17:18:23 -0800 Message-ID: Date: Tue, 5 Dec 2023 09:13:50 +0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Cc: baolu.lu@linux.intel.com, Joerg Roedel , Will Deacon , Robin Murphy , Kevin Tian , Jean-Philippe Brucker , Nicolin Chen , Yi Liu , Jacob Pan , Yan Zhao , iommu@lists.linux.dev, kvm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v7 12/12] iommu: Improve iopf_queue_flush_dev() Content-Language: en-US To: Jason Gunthorpe References: <20231115030226.16700-1-baolu.lu@linux.intel.com> <20231115030226.16700-13-baolu.lu@linux.intel.com> <20231201203536.GG1489931@ziepe.ca> <93a57e63-352c-407c-ac3f-4b91c11d925d@linux.intel.com> <20231204132732.GM1489931@ziepe.ca> From: Baolu Lu In-Reply-To: <20231204132732.GM1489931@ziepe.ca> 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 12/4/23 9:27 PM, Jason Gunthorpe wrote: > On Mon, Dec 04, 2023 at 11:46:30AM +0800, Baolu Lu wrote: >> On 12/2/23 4:35 AM, Jason Gunthorpe wrote: >> I am wondering whether we can take patch 1/12 ~ 10/12 of this series as >> a first step, a refactoring effort to support delivering iopf to >> userspace? I will follow up with one or multiple series to add the >> optimizations. > I think that is reasonable, though I would change the earlier patch to > use RCU to obtain the fault data. All right! I will do this in the updated version. Best regards, baolu