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.5 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, 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 EA6D6C433E0 for ; Wed, 22 Jul 2020 12:19:30 +0000 (UTC) Received: from silver.osuosl.org (smtp3.osuosl.org [140.211.166.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id C5B3620787 for ; Wed, 22 Jul 2020 12:19:30 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org C5B3620787 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=8bytes.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=iommu-bounces@lists.linux-foundation.org Received: from localhost (localhost [127.0.0.1]) by silver.osuosl.org (Postfix) with ESMTP id 695A220425; Wed, 22 Jul 2020 12:19:30 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from silver.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FqfwmmfHTau6; Wed, 22 Jul 2020 12:19:29 +0000 (UTC) Received: from lists.linuxfoundation.org (lf-lists.osuosl.org [140.211.9.56]) by silver.osuosl.org (Postfix) with ESMTP id D3AEF203D0; Wed, 22 Jul 2020 12:19:29 +0000 (UTC) Received: from lf-lists.osuosl.org (localhost [127.0.0.1]) by lists.linuxfoundation.org (Postfix) with ESMTP id 9CABAC004E; Wed, 22 Jul 2020 12:19:29 +0000 (UTC) Received: from silver.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by lists.linuxfoundation.org (Postfix) with ESMTP id E6EDDC004C for ; Wed, 22 Jul 2020 12:19:28 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by silver.osuosl.org (Postfix) with ESMTP id CE748203D0 for ; Wed, 22 Jul 2020 12:19:28 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from silver.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ccK4qNCCT6Il for ; Wed, 22 Jul 2020 12:19:27 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from theia.8bytes.org (8bytes.org [81.169.241.247]) by silver.osuosl.org (Postfix) with ESMTPS id 6672920425 for ; Wed, 22 Jul 2020 12:19:27 +0000 (UTC) Received: by theia.8bytes.org (Postfix, from userid 1000) id E53622C8; Wed, 22 Jul 2020 14:19:23 +0200 (CEST) Date: Wed, 22 Jul 2020 14:19:22 +0200 From: "joro@8bytes.org" To: "Sironi, Filippo" Subject: Re: [PATCH v2 0/3] iommu/amd: I/O VA address limits Message-ID: <20200722121922.GY27672@8bytes.org> References: <20200630093039.GC28824@8bytes.org> <20200630224634.319-1-sebott@amazon.de> <20200710123059.GF27672@8bytes.org> <751e403f-7095-f761-465b-9e187b423b0b@amazon.de> <271d67b2-482e-7a16-8fd7-1f1a6a4bdff2@arm.com> <2a04dcca86bdccece6e0109c30fc0262e1bf8829.camel@amazon.de> <004a060f-823d-af4e-a34d-1ff029faa40f@arm.com> <715c45b76f49b732e5f20157945d2ae262654602.camel@amazon.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <715c45b76f49b732e5f20157945d2ae262654602.camel@amazon.de> User-Agent: Mutt/1.10.1 (2018-07-13) Cc: "Serebrin, Benjamin" , "sebott@amazon.de" , "robin.murphy@arm.com" , "iommu@lists.linux-foundation.org" X-BeenThere: iommu@lists.linux-foundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Development issues for Linux IOMMU support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: iommu-bounces@lists.linux-foundation.org Sender: "iommu" On Fri, Jul 17, 2020 at 03:15:43PM +0000, Sironi, Filippo wrote: > I don't believe that we want to trust a userspace driver here, this may > result in hosts becoming unstable because devices are asked to do things > they aren't meant to do (e.g., DMA beyond 48 bits). How is the hosts stability affected when a device is programmed with handles outside of its DMA mask? Anyway, someone needs to know how to use the device in the end, and this entity also needs to know the DMA mask of the device and pass it down to path to the dma-iommu code. Regards, Joerg _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu