Received: by 2002:a05:6358:53a8:b0:117:f937:c515 with SMTP id z40csp2560313rwe; Sun, 16 Apr 2023 00:06:06 -0700 (PDT) X-Google-Smtp-Source: AKy350apVkqjqNoWOB+4etd4JAgQ7alsTsf0wWmK3739peu2zHg+vAmwcFBkPznem064u7bv374f X-Received: by 2002:a17:903:2443:b0:1a6:b608:5058 with SMTP id l3-20020a170903244300b001a6b6085058mr4922680pls.59.1681628765928; Sun, 16 Apr 2023 00:06:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1681628765; cv=none; d=google.com; s=arc-20160816; b=wlGWdDkCf4oufnlXLib6ekgtsu1feHWWyvO97hyrn4PUMAV/34PwuIunvHvMGdrmai JIhSVfdPSD94RFxUBxRN3Di2Ctmu9etJjwWquK7pPfe77hVQhAB0QHQt5Ii9CG1vwaG0 oStzHGHWOpccKcfFTZEjNk4M6nTdk4esMPpp7FROGaVYC6/uMZHC3qq3K+X4P6Lj67Tf cfMo7fYdgO+j2tDgvbaYvUptocWXP+xispof3KWQvKYyfx6di4UVilJTl2y4D11l1kde 39p4J667Fs6WZ67rN375FAgMHfx21XGd1oT7WW0RXWcdNrp7VO7rdkMJ/FKkwaBRkUmW qytw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=DsAfQ9cs2xYk5wMQhowbXevaKWWKnU7VwU9X73kLblc=; b=jyWdOX1JRHp3Y2FjtRvvmn4BymsajXYIFnhpdtCiBW+fVWhBfCpd7jHlB0bCBuWqYS ksYw4zyLon/NBN9v1aA3ZpcaCtinDvzaZq/GZqo3g2e4yuV8BrUVmiZIOpnacn6eogwc wLtwmcYyG+nJdHh8PTiFUzvOoM5IsU+eEeiXvWCqdSnF5r/jlP38WZihPow2gkfqmjvf LYvPYVleK2SXjNtPnt5DOcrRlErsp46BAd/Apsa3pie7PnLB0cDhC/pDVQ2ZmGzKB4vP U0+K5V65zZ2Lo21S03dGIyK4Nrdt6JYkldDy8R5l/tKvY17wO0m2mwi7XJYKqoRZ6etv xzTA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id a16-20020a170902ecd000b001a04212a4b1si9763078plh.439.2023.04.16.00.05.32; Sun, 16 Apr 2023 00:06:05 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230146AbjDPGmC (ORCPT + 99 others); Sun, 16 Apr 2023 02:42:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49976 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229582AbjDPGmA (ORCPT ); Sun, 16 Apr 2023 02:42:00 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D60A82D73; Sat, 15 Apr 2023 23:41:59 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id 8649C67373; Sun, 16 Apr 2023 08:41:56 +0200 (CEST) Date: Sun, 16 Apr 2023 08:41:56 +0200 From: Christoph Hellwig To: Robin Murphy Cc: Christoph Hellwig , Linux regressions mailing list , LKML , Linux PCI , iommu@lists.linux.dev, baolu.lu@linux.intel.com Subject: Re: [regression] Bug 217218 - Trying to boot Linux version 6-2.2 kernel with Marvell SATA controller 88SE9235 Message-ID: <20230416064156.GA6410@lst.de> References: <20230328012231.GB21977@lst.de> <01c50370-002d-5e18-3edc-81c9527aedc9@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01c50370-002d-5e18-3edc-81c9527aedc9@arm.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 30, 2023 at 01:18:45PM +0100, Robin Murphy wrote: > FWIW "Marvell SATA" instantly makes me suspect the phantom function quirk. > What *should* happen is the IOMMU driver sees the PCI DMA aliases correctly > and sets up context entries for both 07.00.0 and 07.00.1, but it looks like > that may be what's gone awry. Looking at the bug report it seems this is device 9235, which doesn't need the DMA alias quirks.