From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from new4-smtp.messagingengine.com (new4-smtp.messagingengine.com [66.111.4.230]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E43D6173 for ; Tue, 25 Jan 2022 00:44:49 +0000 (UTC) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id 8BAC1580389; Mon, 24 Jan 2022 19:44:48 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 24 Jan 2022 19:44:48 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=turner.link; h= cc:cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; bh=Hg+/kJzRpMwyU8RBBG9lM29Q4G3SCNyE5PQExK Qjrjg=; b=BqhV2/LX+jA/ib0C3suNSFwh8doiJauUSvPVxk+uBbNEorrAZbP1iR 5gNpFk2LgQ7cLfef4t7YtlVJSeAE1tg7pNCtVRYvd5IfU96XR2wTMxWkt5EgqN5O xbZYT20AVlZSDY6PPGchtxHvVVZxZh+6cPw4ahe/8gK2gmshQA7Rb5oAruoy5iD9 0lpJlFpQzx8xBboXOi81OZfCQl5D2CoNFJMi4EUzEbEORp5XHpGY1Ae0zEJQFMcG irXojU99SQzfbYshiyxeHeKgyKApQLq43HdA+0p7iRoIL+aYSMhIDLLINo475C4T JiMKE71bQGkV8LTe7hWUbRgrjFnaiyOg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=Hg+/kJzRpMwyU8RBB G9lM29Q4G3SCNyE5PQExKQjrjg=; b=NnF9YKvTgV+/CzqonPrhH6bqt2WlJ4u/V 0e5EIJr4hxAwC9+fPKCyjMjLQFL7qrbjxjXFIPrdrUTGfM7J6s3SHwnq67rYY35f AAdyTDYdeqWTj4LCnd+TZ70KSgKLAVdSglmbXgwa+ajA6n/uUMX1EpFmSlYkwj/D w8Xjd3ybbGdoY1DGBiQn2dxoQV8DpbD0T3IQ2uw6cxeFgp9p/TCwyaO+BhzpE0mF LxR/XD6IxXdjTGUUAozzYQknbIZf0gvWcm4ExzybZRggNr/xbIys/rnbBcng0jOh pyPxkrjIS0E8x1ywdW+MBOVpvlDmppAIOE3MijQ16LRpMyXnYn9Yw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrvdekgddvhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpehfhffvufffjgfkgggtsehttdertddttddtnecuhfhrohhmpeflrghmvghsucfv uhhrnhgvrhcuoehlihhnuhigkhgvrhhnvghlrdhfohhsshesughmrghrtgdqnhhonhgvrd htuhhrnhgvrhdrlhhinhhkqeenucggtffrrghtthgvrhhnpeetvdefudehieeufefghfdv teeitddtvefhieetuefhleevudevtddtfffggffgteenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehlihhnuhigkhgvrhhnvghlrdhfohhsshes ughmrghrtgdqnhhonhgvrdhtuhhrnhgvrhdrlhhinhhk X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 24 Jan 2022 19:44:47 -0500 (EST) References: <87ee57c8fu.fsf@turner.link> <87a6ftk9qy.fsf@dmarc-none.turner.link> <87zgnp96a4.fsf@turner.link> <87czkk1pmt.fsf@dmarc-none.turner.link> <87sftfqwlx.fsf@dmarc-none.turner.link> From: James Turner To: "Lazar, Lijo" Cc: Alex Deucher , Thorsten Leemhuis , "Deucher, Alexander" , "regressions@lists.linux.dev" , "kvm@vger.kernel.org" , Greg KH , "Pan, Xinhui" , LKML , "amd-gfx@lists.freedesktop.org" , Alex Williamson , "Koenig, Christian" Subject: Re: [REGRESSION] Too-low frequency limit for AMD GPU PCI-passed-through to Windows VM Date: Mon, 24 Jan 2022 18:58:10 -0500 In-reply-to: Message-ID: <87ee4wprsx.fsf@turner.link> Precedence: bulk X-Mailing-List: regressions@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain Hi Lijo, > Not able to relate to how it affects gfx/mem DPM alone. Unless Alex > has other ideas, would you be able to enable drm debug messages and > share the log? Sure, I'm happy to provide drm debug messages. Enabling everything (0x1ff) generates *a lot* of log messages, though. Is there a smaller subset that would be useful? Fwiw, I don't see much in the full drm logs about the AMD GPU anyway; it's mostly about the Intel GPU. All the messages in the system log containing "01:00" or "1002:6981" are identical between the two versions. I've posted below the only places in the logs which contain "amd". The commit with the issue (f9b7f3703ff9) has a few drm log messages from amdgpu which are not present in the logs for f1688bd69ec4. # f1688bd69ec4 ("drm/amd/amdgpu:save psp ring wptr to avoid attack") [drm] amdgpu kernel modesetting enabled. vga_switcheroo: detected switching method \_SB_.PCI0.GFX0.ATPX handle ATPX version 1, functions 0x00000033 amdgpu: CRAT table not found amdgpu: Virtual CRAT table created for CPU amdgpu: Topology: Add CPU node # f9b7f3703ff9 ("drm/amdgpu/acpi: make ATPX/ATCS structures global (v2)") [drm] amdgpu kernel modesetting enabled. vga_switcheroo: detected switching method \_SB_.PCI0.GFX0.ATPX handle ATPX version 1, functions 0x00000033 [drm:amdgpu_atif_pci_probe_handle.isra.0 [amdgpu]] Found ATIF handle \_SB_.PCI0.GFX0.ATIF [drm:amdgpu_atif_pci_probe_handle.isra.0 [amdgpu]] ATIF version 1 [drm:amdgpu_acpi_detect [amdgpu]] SYSTEM_PARAMS: mask = 0x6, flags = 0x7 [drm:amdgpu_acpi_detect [amdgpu]] Notification enabled, command code = 0xd9 amdgpu: CRAT table not found amdgpu: Virtual CRAT table created for CPU amdgpu: Topology: Add CPU node Other things I'm willing to try if they'd be useful: - I could update to the 21.Q4 Radeon Pro driver in the Windows VM. (The 21.Q3 driver is currently installed.) - I could set up a Linux guest VM with PCI passthrough to compare to the Windows VM and obtain more debugging information. - I could build a kernel with a patch applied, e.g. to disable some of the changes in f9b7f3703ff9. James 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 Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id BDC2EC4332F for ; Tue, 25 Jan 2022 08:57:25 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 383D910EE17; Tue, 25 Jan 2022 08:57:25 +0000 (UTC) Received: from new4-smtp.messagingengine.com (new4-smtp.messagingengine.com [66.111.4.230]) by gabe.freedesktop.org (Postfix) with ESMTPS id E043110E2DF for ; Tue, 25 Jan 2022 00:44:50 +0000 (UTC) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id 8BAC1580389; Mon, 24 Jan 2022 19:44:48 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 24 Jan 2022 19:44:48 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=turner.link; h= cc:cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; bh=Hg+/kJzRpMwyU8RBBG9lM29Q4G3SCNyE5PQExK Qjrjg=; b=BqhV2/LX+jA/ib0C3suNSFwh8doiJauUSvPVxk+uBbNEorrAZbP1iR 5gNpFk2LgQ7cLfef4t7YtlVJSeAE1tg7pNCtVRYvd5IfU96XR2wTMxWkt5EgqN5O xbZYT20AVlZSDY6PPGchtxHvVVZxZh+6cPw4ahe/8gK2gmshQA7Rb5oAruoy5iD9 0lpJlFpQzx8xBboXOi81OZfCQl5D2CoNFJMi4EUzEbEORp5XHpGY1Ae0zEJQFMcG irXojU99SQzfbYshiyxeHeKgyKApQLq43HdA+0p7iRoIL+aYSMhIDLLINo475C4T JiMKE71bQGkV8LTe7hWUbRgrjFnaiyOg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=Hg+/kJzRpMwyU8RBB G9lM29Q4G3SCNyE5PQExKQjrjg=; b=NnF9YKvTgV+/CzqonPrhH6bqt2WlJ4u/V 0e5EIJr4hxAwC9+fPKCyjMjLQFL7qrbjxjXFIPrdrUTGfM7J6s3SHwnq67rYY35f AAdyTDYdeqWTj4LCnd+TZ70KSgKLAVdSglmbXgwa+ajA6n/uUMX1EpFmSlYkwj/D w8Xjd3ybbGdoY1DGBiQn2dxoQV8DpbD0T3IQ2uw6cxeFgp9p/TCwyaO+BhzpE0mF LxR/XD6IxXdjTGUUAozzYQknbIZf0gvWcm4ExzybZRggNr/xbIys/rnbBcng0jOh pyPxkrjIS0E8x1ywdW+MBOVpvlDmppAIOE3MijQ16LRpMyXnYn9Yw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrvdekgddvhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpehfhffvufffjgfkgggtsehttdertddttddtnecuhfhrohhmpeflrghmvghsucfv uhhrnhgvrhcuoehlihhnuhigkhgvrhhnvghlrdhfohhsshesughmrghrtgdqnhhonhgvrd htuhhrnhgvrhdrlhhinhhkqeenucggtffrrghtthgvrhhnpeetvdefudehieeufefghfdv teeitddtvefhieetuefhleevudevtddtfffggffgteenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehlihhnuhigkhgvrhhnvghlrdhfohhsshes ughmrghrtgdqnhhonhgvrdhtuhhrnhgvrhdrlhhinhhk X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 24 Jan 2022 19:44:47 -0500 (EST) References: <87ee57c8fu.fsf@turner.link> <87a6ftk9qy.fsf@dmarc-none.turner.link> <87zgnp96a4.fsf@turner.link> <87czkk1pmt.fsf@dmarc-none.turner.link> <87sftfqwlx.fsf@dmarc-none.turner.link> From: James Turner To: "Lazar, Lijo" Subject: Re: [REGRESSION] Too-low frequency limit for AMD GPU PCI-passed-through to Windows VM Date: Mon, 24 Jan 2022 18:58:10 -0500 In-reply-to: Message-ID: <87ee4wprsx.fsf@turner.link> MIME-Version: 1.0 Content-Type: text/plain X-Mailman-Approved-At: Tue, 25 Jan 2022 08:57:22 +0000 X-BeenThere: amd-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion list for AMD gfx List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "regressions@lists.linux.dev" , "kvm@vger.kernel.org" , Greg KH , "Pan, Xinhui" , LKML , "amd-gfx@lists.freedesktop.org" , "Deucher, Alexander" , Alex Williamson , Thorsten Leemhuis , Alex Deucher , "Koenig, Christian" Errors-To: amd-gfx-bounces@lists.freedesktop.org Sender: "amd-gfx" Hi Lijo, > Not able to relate to how it affects gfx/mem DPM alone. Unless Alex > has other ideas, would you be able to enable drm debug messages and > share the log? Sure, I'm happy to provide drm debug messages. Enabling everything (0x1ff) generates *a lot* of log messages, though. Is there a smaller subset that would be useful? Fwiw, I don't see much in the full drm logs about the AMD GPU anyway; it's mostly about the Intel GPU. All the messages in the system log containing "01:00" or "1002:6981" are identical between the two versions. I've posted below the only places in the logs which contain "amd". The commit with the issue (f9b7f3703ff9) has a few drm log messages from amdgpu which are not present in the logs for f1688bd69ec4. # f1688bd69ec4 ("drm/amd/amdgpu:save psp ring wptr to avoid attack") [drm] amdgpu kernel modesetting enabled. vga_switcheroo: detected switching method \_SB_.PCI0.GFX0.ATPX handle ATPX version 1, functions 0x00000033 amdgpu: CRAT table not found amdgpu: Virtual CRAT table created for CPU amdgpu: Topology: Add CPU node # f9b7f3703ff9 ("drm/amdgpu/acpi: make ATPX/ATCS structures global (v2)") [drm] amdgpu kernel modesetting enabled. vga_switcheroo: detected switching method \_SB_.PCI0.GFX0.ATPX handle ATPX version 1, functions 0x00000033 [drm:amdgpu_atif_pci_probe_handle.isra.0 [amdgpu]] Found ATIF handle \_SB_.PCI0.GFX0.ATIF [drm:amdgpu_atif_pci_probe_handle.isra.0 [amdgpu]] ATIF version 1 [drm:amdgpu_acpi_detect [amdgpu]] SYSTEM_PARAMS: mask = 0x6, flags = 0x7 [drm:amdgpu_acpi_detect [amdgpu]] Notification enabled, command code = 0xd9 amdgpu: CRAT table not found amdgpu: Virtual CRAT table created for CPU amdgpu: Topology: Add CPU node Other things I'm willing to try if they'd be useful: - I could update to the 21.Q4 Radeon Pro driver in the Windows VM. (The 21.Q3 driver is currently installed.) - I could set up a Linux guest VM with PCI passthrough to compare to the Windows VM and obtain more debugging information. - I could build a kernel with a patch applied, e.g. to disable some of the changes in f9b7f3703ff9. James