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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CFD17C433EF for ; Wed, 17 Nov 2021 14:15:20 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id B2A6161B54 for ; Wed, 17 Nov 2021 14:15:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238293AbhKQOSS (ORCPT ); Wed, 17 Nov 2021 09:18:18 -0500 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:29436 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238274AbhKQOSK (ORCPT ); Wed, 17 Nov 2021 09:18:10 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1637158510; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=NDuAh9ydG33nQ/5kdKqaUb4pA1g/jsmhAD4nowtB8q0=; b=dNdy4Mz31I46s5l+sggVpmAsEQyAOnEll6D9rk2qkC4Ov4ptBmSNK3NsomPSmpwGvnA3+m AtWWOl4tSl4cMcdhslXatFCsaYeO0hazQ82kucZ+90aeKBwELErXsnESMfVAMmTTwVKfE/ Y6Fc7/dTrtAQeIqydZAdg+I1/083vVA= Received: from mail-ot1-f72.google.com (mail-ot1-f72.google.com [209.85.210.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-587-GisoXbBfMDSo-1qxn7FKeA-1; Wed, 17 Nov 2021 09:15:09 -0500 X-MC-Unique: GisoXbBfMDSo-1qxn7FKeA-1 Received: by mail-ot1-f72.google.com with SMTP id w23-20020a056830411700b00564e73edd41so1787049ott.21 for ; Wed, 17 Nov 2021 06:15:09 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:organization:mime-version:content-transfer-encoding; bh=NDuAh9ydG33nQ/5kdKqaUb4pA1g/jsmhAD4nowtB8q0=; b=5WdT8j7olih0A9Nt1EVRItCC0vbGzKlTpCCBSb1l5OomCLa9JySQu4WzmVH/2U5DK6 JyDI3/9oAXEVeJP3Svr4TZ9IdDv+kXT01gyN4dNsHMbOou9/MPdpShjdpzX05zTyTq// jBOCCMcxpueLBATv+xo/0N8p1ZqS3Kax9qVwFaXNFBH/sLpL7ySBxcQTcKl8UAzOlyDt 4o4l4F3LDFHdqfaqapK8QwYoyvylbsiRu1TYdcSRf13mvoxsxIUvuXoUaDVDBW+yXyes galDZReer4JTcjfvoux5rcoANhL/59LMYnHARTgBKL1ufu4exfBIzyhL7J3J7O+U/hTl Lwfw== X-Gm-Message-State: AOAM531ahttNb0YRh+a1jLS6jISYWtqUH0Pn0620odqWX7kaNECKPjun E48vQI6zT1EUBHw1JR6kx4JtLxNurhE1uCoYOYLZoKlwrSeAYxvQOfi+jKS5Uqw8FWhXbLwhL/0 mqgTKBr+okFxd28RQZmYbKzT7 X-Received: by 2002:a05:6808:178d:: with SMTP id bg13mr14567850oib.171.1637158508616; Wed, 17 Nov 2021 06:15:08 -0800 (PST) X-Google-Smtp-Source: ABdhPJzIUkaPo+5JL68yqcgqUWzhvxOFFi1URuQME7OdHfDKEYHYLEe4Wuvsx7qhQJwyhWqct3Uphg== X-Received: by 2002:a05:6808:178d:: with SMTP id bg13mr14567818oib.171.1637158508414; Wed, 17 Nov 2021 06:15:08 -0800 (PST) Received: from redhat.com ([38.15.36.239]) by smtp.gmail.com with ESMTPSA id s17sm2319497ooj.42.2021.11.17.06.15.07 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 17 Nov 2021 06:15:08 -0800 (PST) Date: Wed, 17 Nov 2021 07:15:07 -0700 From: Alex Williamson To: Christoph Hellwig Cc: Yifeng Li , Bjorn Helgaas , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org Subject: Re: [PATCH v2] PCI: Add func1 DMA quirk for Marvell 88SE9125 SATA controller Message-ID: <20211117071507.775e12b8.alex.williamson@redhat.com> In-Reply-To: References: Organization: Red Hat MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 17 Nov 2021 02:12:04 -0800 Christoph Hellwig wrote: > On Tue, Nov 16, 2021 at 02:32:26PM +0000, Yifeng Li wrote: > > Like other SATA controller chips in the Marvell 88SE91xx series, the > > Marvell 88SE9125 has the same DMA requester ID hardware bug that prevents > > it from working under IOMMU. This patch adds its device ID 0x9125 to the > > Function 1 DMA alias quirk list. > > Btw, do we need to prevent vfio assignment for all devices with this > quirk? No, the alias is taken into account with grouping and IOMMU programming, it should work with vfio. Thanks, Alex