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 X-Spam-Level: X-Spam-Status: No, score=-5.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8B582C433E9 for ; Thu, 18 Mar 2021 12:48:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 5672964F70 for ; Thu, 18 Mar 2021 12:48:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231308AbhCRMsH (ORCPT ); Thu, 18 Mar 2021 08:48:07 -0400 Received: from szxga04-in.huawei.com ([45.249.212.190]:14091 "EHLO szxga04-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230477AbhCRMri (ORCPT ); Thu, 18 Mar 2021 08:47:38 -0400 Received: from DGGEMS404-HUB.china.huawei.com (unknown [172.30.72.60]) by szxga04-in.huawei.com (SkyGuard) with ESMTP id 4F1RZq72Rsz19GKH; Thu, 18 Mar 2021 20:45:39 +0800 (CST) Received: from [10.174.184.135] (10.174.184.135) by DGGEMS404-HUB.china.huawei.com (10.3.19.204) with Microsoft SMTP Server id 14.3.498.0; Thu, 18 Mar 2021 20:47:27 +0800 Subject: Re: [RFC PATCH v1 0/4] vfio: Add IOPF support for VFIO passthrough To: "Tian, Kevin" , Alex Williamson CC: Cornelia Huck , "kvm@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Jean-Philippe Brucker , Eric Auger , Lu Baolu , "wanghaibin.wang@huawei.com" , "yuzenghui@huawei.com" , "Liu, Yi L" , "Pan, Jacob jun" References: <20210125090402.1429-1-lushenming@huawei.com> <20210129155730.3a1d49c5@omen.home.shazbot.org> <47bf7612-4fb0-c0bb-fa19-24c4e3d01d3f@huawei.com> <4f904b23-e434-d42b-15a9-a410f3b4edb9@huawei.com> From: Shenming Lu Message-ID: <4e2c9f05-9a87-4aca-71d3-c329d7638aae@huawei.com> Date: Thu, 18 Mar 2021 20:47:16 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.2.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.174.184.135] X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On 2021/3/18 20:32, Tian, Kevin wrote: >> From: Shenming Lu >> Sent: Thursday, March 18, 2021 7:54 PM >> >> On 2021/3/18 17:07, Tian, Kevin wrote: >>>> From: Shenming Lu >>>> Sent: Thursday, March 18, 2021 3:53 PM >>>> >>>> On 2021/2/4 14:52, Tian, Kevin wrote:>>> In reality, many >>>>>>> devices allow I/O faulting only in selective contexts. However, there >>>>>>> is no standard way (e.g. PCISIG) for the device to report whether >>>>>>> arbitrary I/O fault is allowed. Then we may have to maintain device >>>>>>> specific knowledge in software, e.g. in an opt-in table to list devices >>>>>>> which allows arbitrary faults. For devices which only support selective >>>>>>> faulting, a mediator (either through vendor extensions on vfio-pci-core >>>>>>> or a mdev wrapper) might be necessary to help lock down non- >> faultable >>>>>>> mappings and then enable faulting on the rest mappings. >>>>>> >>>>>> For devices which only support selective faulting, they could tell it to the >>>>>> IOMMU driver and let it filter out non-faultable faults? Do I get it wrong? >>>>> >>>>> Not exactly to IOMMU driver. There is already a vfio_pin_pages() for >>>>> selectively page-pinning. The matter is that 'they' imply some device >>>>> specific logic to decide which pages must be pinned and such knowledge >>>>> is outside of VFIO. >>>>> >>>>> From enabling p.o.v we could possibly do it in phased approach. First >>>>> handles devices which tolerate arbitrary DMA faults, and then extends >>>>> to devices with selective-faulting. The former is simpler, but with one >>>>> main open whether we want to maintain such device IDs in a static >>>>> table in VFIO or rely on some hints from other components (e.g. PF >>>>> driver in VF assignment case). Let's see how Alex thinks about it. >>>> >>>> Hi Kevin, >>>> >>>> You mentioned selective-faulting some time ago. I still have some doubt >>>> about it: >>>> There is already a vfio_pin_pages() which is used for limiting the IOMMU >>>> group dirty scope to pinned pages, could it also be used for indicating >>>> the faultable scope is limited to the pinned pages and the rest mappings >>>> is non-faultable that should be pinned and mapped immediately? But it >>>> seems to be a little weird and not exactly to what you meant... I will >>>> be grateful if you can help to explain further. :-) >>>> >>> >>> The opposite, i.e. the vendor driver uses vfio_pin_pages to lock down >>> pages that are not faultable (based on its specific knowledge) and then >>> the rest memory becomes faultable. >> >> Ahh... >> Thus, from the perspective of VFIO IOMMU, if IOPF enabled for such device, >> only the page faults within the pinned range are valid in the registered >> iommu fault handler... >> I have another question here, for the IOMMU backed devices, they are >> already >> all pinned and mapped when attaching, is there a need to call >> vfio_pin_pages() >> to lock down pages for them? Did I miss something?... >> > > If a device is marked as supporting I/O page fault (fully or selectively), > there should be no pinning at attach or DMA_MAP time (suppose as > this series does). Then for devices with selective-faulting its vendor > driver will lock down the pages which are not faultable at run-time, > e.g. when intercepting guest registration of a ring buffer... Get it. Thanks a lot for this! :-) Shenming > > Thanks > Kevin >