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=-0.6 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 92B58C432C0 for ; Wed, 4 Dec 2019 04:37:12 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (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 3D84A20640 for ; Wed, 4 Dec 2019 04:37:12 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=anastas.io header.i=@anastas.io header.b="RX2KsrOy" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3D84A20640 Authentication-Results: mail.kernel.org; dmarc=fail (p=quarantine dis=none) header.from=anastas.io Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from lists.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 47SR062slZzDqSK for ; Wed, 4 Dec 2019 15:37:10 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=anastas.io (client-ip=104.248.188.109; helo=alpha.anastas.io; envelope-from=shawn@anastas.io; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=pass (p=quarantine dis=none) header.from=anastas.io Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=anastas.io header.i=@anastas.io header.b="RX2KsrOy"; dkim-atps=neutral Received: from alpha.anastas.io (alpha.anastas.io [104.248.188.109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 47SQw83ff5zDqT6 for ; Wed, 4 Dec 2019 15:33:44 +1100 (AEDT) Received: from authenticated-user (alpha.anastas.io [104.248.188.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by alpha.anastas.io (Postfix) with ESMTPSA id 9CFD77F435; Tue, 3 Dec 2019 17:45:53 -0600 (CST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=anastas.io; s=mail; t=1575416754; bh=mdtQhN24kYvuo/KKla+16YACVSx83u/SxcWjz3GMu8E=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=RX2KsrOyELqDyJKEfd8W1Ers5uUuvDUvvfYAFg6XgbIbA6Dckey5KVjDPF74PcUBQ NrHiAQZXIghL9EKTMP07O+k0eb/vwAr1tssHj22vWiosLf69W7T4EwTVX9piAEMtVP 228LLnFgFxu0x4csQBxyuCDhkpFh/eZjtXIgvNrZUHw6Ips2d5QybFhqXfH2NQI5AW 3RwRGMpBvyTTJRvNg1aABPio/OZ0n6+jED1XJr6MGrAw/JbsfWdH91f2dUhmehhqFF S2fBn2luLsnpXlEz/fB6vo4IH6DqHC9NkZ004KLil1717rrwCcntluSekIf6RdjDss Nukga9XSlvFIA== Subject: Re: [PATCH v2 1/3] powernv/iov: Ensure the pdn for VFs always contains a valid PE number To: Oliver O'Halloran , linuxppc-dev@lists.ozlabs.org References: <20191028085424.12006-1-oohall@gmail.com> From: Shawn Anastasio Message-ID: <166b9ee3-08fe-e558-b6a3-4ea5d9b9219f@anastas.io> Date: Tue, 3 Dec 2019 17:45:51 -0600 MIME-Version: 1.0 In-Reply-To: <20191028085424.12006-1-oohall@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: aik@ozlabs.ru, linux-pci@vger.kernel.org Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On 10/28/19 3:54 AM, Oliver O'Halloran wrote: > On pseries there is a bug with adding hotplugged devices to an IOMMU group. > For a number of dumb reasons fixing that bug first requires re-working how > VFs are configured on PowerNV. Are these patches expected to land soon, or is there another fix in the pipeline? As far as I can tell this is still an issue.