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 lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id E2A87C433F5 for ; Fri, 17 Dec 2021 14:43:46 +0000 (UTC) Received: from list by lists.xenproject.org with outflank-mailman.248698.428978 (Exim 4.92) (envelope-from ) id 1myESD-00061a-T5; Fri, 17 Dec 2021 14:43:25 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 248698.428978; Fri, 17 Dec 2021 14:43:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1myESD-00061T-Pz; Fri, 17 Dec 2021 14:43:25 +0000 Received: by outflank-mailman (input) for mailman id 248698; Fri, 17 Dec 2021 14:43:24 +0000 Received: from mail.xenproject.org ([104.130.215.37]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1myESC-00061N-8y for xen-devel@lists.xenproject.org; Fri, 17 Dec 2021 14:43:24 +0000 Received: from xenbits.xenproject.org ([104.239.192.120]) by mail.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1myES9-00054C-UG; Fri, 17 Dec 2021 14:43:21 +0000 Received: from 54-240-197-239.amazon.com ([54.240.197.239] helo=[192.168.25.72]) by xenbits.xenproject.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1myES9-0007gr-N8; Fri, 17 Dec 2021 14:43:21 +0000 X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=xen.org; s=20200302mail; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From: References:Cc:To:Subject:MIME-Version:Date:Message-ID; bh=45fT3HZdmHIyU5+qdTRu8J/nl+vxCT+pYN8JBODCuFA=; b=BbfoiSIQsDLab2mm7B0wosAHPH 8dvN3mfu7RoTQIPeHF0ZCWnIa4YpSTwGSjHP/7AedZhIIyUzhA4I7PHHsxWaeGagmPfoJMi1dzXWz 5ewLpSeUiBjuow7AnexmhbEBQ1MRIAsvM2l9Z3jiTIBLDOn1obEWpeLriO+heb/RLJH4=; Message-ID: Date: Fri, 17 Dec 2021 14:43:19 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.4.0 Subject: Re: [PATCH v2 03/18] IOMMU: have vendor code announce supported page sizes To: Jan Beulich , "xen-devel@lists.xenproject.org" Cc: Andrew Cooper , Paul Durrant , Kevin Tian , Stefano Stabellini , Volodymyr Babchuk , Bertrand Marquis , Rahul Singh References: <957f067b-9fe1-2350-4266-51982f09d3a9@suse.com> <3f0adf5b-cc2a-1b72-8376-baad574fa824@suse.com> From: Julien Grall In-Reply-To: <3f0adf5b-cc2a-1b72-8376-baad574fa824@suse.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi Jan, On 24/09/2021 10:43, Jan Beulich wrote: > Generic code will use this information to determine what order values > can legitimately be passed to the ->{,un}map_page() hooks. For now all > ops structures simply get to announce 4k mappings (as base page size), > and there is (and always has been) an assumption that this matches the > CPU's MMU base page size (eventually we will want to permit IOMMUs with > a base page size smaller than the CPU MMU's). > > Signed-off-by: Jan Beulich > Reviewed-by: Kevin Tian Acked-by: Julien Grall Cheers, -- Julien Grall