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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9FC0BC433EF for ; Tue, 15 Feb 2022 14:57:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239386AbiBOO5R (ORCPT ); Tue, 15 Feb 2022 09:57:17 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:43022 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235008AbiBOO5O (ORCPT ); Tue, 15 Feb 2022 09:57:14 -0500 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8234::]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CC6801001; Tue, 15 Feb 2022 06:57:00 -0800 (PST) Received: from ip4d144895.dynamic.kabel-deutschland.de ([77.20.72.149] helo=[192.168.66.200]); authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1nJzGD-0005P7-Tf; Tue, 15 Feb 2022 15:56:57 +0100 Message-ID: <5a68afe4-1e9e-c683-e06d-30afc2156f14@leemhuis.info> Date: Tue, 15 Feb 2022 15:56:56 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: [REGRESSION] Too-low frequency limit for AMD GPU PCI-passed-through to Windows VM Content-Language: en-BS To: Jim Turner , "Lazar, Lijo" Cc: Alex Deucher , "Deucher, Alexander" , "regressions@lists.linux.dev" , "kvm@vger.kernel.org" , Greg KH , "Pan, Xinhui" , LKML , "amd-gfx@lists.freedesktop.org" , Alex Williamson , "Koenig, Christian" 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> <87ee4wprsx.fsf@turner.link> <4b3ed7f6-d2b6-443c-970e-d963066ebfe3@amd.com> <87pmo8r6ob.fsf@turner.link> From: Thorsten Leemhuis In-Reply-To: <87pmo8r6ob.fsf@turner.link> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1644937021;56b63272; X-HE-SMSGID: 1nJzGD-0005P7-Tf Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Top-posting for once, to make this easy accessible to everyone. Nothing happened here for two weeks now afaics. Was the discussion moved elsewhere or did it fall through the cracks? Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) P.S.: As the Linux kernel's regression tracker I'm getting a lot of reports on my table. I can only look briefly into most of them and lack knowledge about most of the areas they concern. I thus unfortunately will sometimes get things wrong or miss something important. I hope that's not the case here; if you think it is, don't hesitate to tell me in a public reply, it's in everyone's interest to set the public record straight. On 30.01.22 01:25, Jim Turner wrote: > Hi Lijo, > >> Specifically, I was looking for any events happening at these two >> places because of the patch- >> >> https://elixir.bootlin.com/linux/v5.16/source/drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c#L411 >> >> https://elixir.bootlin.com/linux/v5.16/source/drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c#L653 > > I searched the logs generated with all drm debug messages enabled > (drm.debug=0x1ff) for "device_class", "ATCS", "atcs", "ATIF", and > "atif", for both f1688bd69ec4 and f9b7f3703ff9. Other than the few lines > mentioning ATIF from my previous email, there weren't any matches. > > Since "device_class" didn't appear in the logs, we know that > `amdgpu_atif_handler` was not called for either version. > > I also patched f9b7f3703ff9 to add the line > > DRM_DEBUG_DRIVER("Entered amdgpu_acpi_pcie_performance_request"); > > at the top (below the variable declarations) of > `amdgpu_acpi_pcie_performance_request`, and then tested again with all > drm debug messages enabled (0x1ff). That debug message didn't show up. > > So, `amdgpu_acpi_pcie_performance_request` was not called either, at > least with f9b7f3703ff9. (I didn't try adding this patch to > f1688bd69ec4.) > > Would anything else be helpful?