Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp628667pxb; Tue, 1 Feb 2022 07:17:15 -0800 (PST) X-Google-Smtp-Source: ABdhPJyc9bjS6KSkUVBsk2hy5UWn0j6jNxeFPpu13JrlU99cARPXktSrF8uJ8W2/LndEOGcstITW X-Received: by 2002:a05:6402:354d:: with SMTP id f13mr25807141edd.40.1643728635176; Tue, 01 Feb 2022 07:17:15 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643728635; cv=none; d=google.com; s=arc-20160816; b=GdOnB6xDUWHWM3xAzN4A+4oDohQ5eowbBGCJvMJb2wSliDqAcpJ4UtzY9zuhoy3cjF Dfa3N+yDULDdLAFWobwTCbN1sUAJVcvpcM3LcBPIzzHysaoH0yHEMRGgf0enyQ9HDF+W 0k9DHqDNqFo+y7c0UoH7LxiGpBUlDA4bdm++vwD0eqvOq9n4yCdv+HFkrvIdjuE++4vb sBsMSfJwytEA8B502WDn0pABoKOTxVEqAfryKfoN0udqX0GS4gZD7ULp3h4Ngt8D8Jgc 2H0e6QUJiP+k0FzqA3pCYnj8hRMpOVk1T/pxpvZTQfYjJ1OIghvwim41Ezmh4T5kqNNF Onnw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:in-reply-to:date:subject :cc:to:from:references:dkim-signature:dkim-signature; bh=P9iOim4NrWctmEwZ8zPw3HEkn6EbbINyR5zkQ223ptE=; b=ldOvzsr5kkSSUP/zh2TSocpR0LHO7SI0xqtlEPL7/3PkTyDNfaCmnRxW7jsYJayAgQ MB/SZp5TqRCkYsIckXnDosJ0wspr7Ro2CHVsyrLp6COze/sCL6Ggky3S317ba0Z7f1MY O9KmfMSnM/bHdnZuCn85v5H/JNrlzHXMyXP2jArQf3KUGDieP5nwsI7x4UTz0sybu/wj DwfN4S36EbwKDGuaeljM4bNq1nIsEnzOMMhVWqPrD0DAqz4ymXj6qd/xdnJAleCiqCEc HlpAspVCvkPc7MF02y4RHOxaFtaEkaqCGWZv3ObVngNmjCV6ViC3NuqkwKhhZSikkdwu iP7A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@turner.link header.s=fm1 header.b=WhZLbraC; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=drCIdtq5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=dmarc-none.turner.link Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id sb22si10309542ejc.439.2022.02.01.07.16.48; Tue, 01 Feb 2022 07:17:15 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@turner.link header.s=fm1 header.b=WhZLbraC; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=drCIdtq5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=dmarc-none.turner.link Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1357302AbiAaCQY (ORCPT + 99 others); Sun, 30 Jan 2022 21:16:24 -0500 Received: from new3-smtp.messagingengine.com ([66.111.4.229]:33883 "EHLO new3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233994AbiAaCQW (ORCPT ); Sun, 30 Jan 2022 21:16:22 -0500 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailnew.nyi.internal (Postfix) with ESMTP id C60A95800EF; Sun, 30 Jan 2022 21:16:21 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Sun, 30 Jan 2022 21:16:21 -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=P9iOim4NrWctmEwZ8zPw3HEkn6EbbINyR5zkQ2 23ptE=; b=WhZLbraCfAbAiaXMYxdU0JtimnEgffIECycU2prEgxs57Qiv3otomd LxciAIQ404Tr+R0QA39S0Sh6TphRwSsKbTW/YyVossjjt9UUp71KVqGDjZU9ha2o 5kIawzsFib+RlISzbDxQ5dboN1jldudrXsbVhsDG+LAGRN7ibAMaNBi9eIvrejU3 TZwuD2V1Eh8s5VjcaN+mbp91bSPGhAFy5e8xxRyR6lHU7Fgs0FCJehomiy708/iL WotvDHVyRRIPtZo83WBNjzbFgp63qAcmVRjLU0+Zr2lsIUskSzgsjSJ1RqxT/LJc YNOPuVMLmuTLqq5zGyYgqMP+g1t6LuAg== 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=P9iOim4NrWctmEwZ8 zPw3HEkn6EbbINyR5zkQ223ptE=; b=drCIdtq56LgKKAk04BhqRdtXtrABgGh37 2dky3hCczhXDUV0ToEuDeuG4UJO94oDrN1SsnA8QQX5xq5xAjL0K/CEHgYwergbJ 1LpooZ28Gk0+tnyKL0jADrmqTwREg3XvV86Tj1NhzvO9a53TDiCWxd5OsUKBQBLM dLKo/cF+OCSUk8yaumj02qn5zLVMpqLrpMDr00Hy+0CdfnrjHp7xkGVQQ7x08+jD 7+in0yYBg4ohQs9Ffyhjvi742vXn8PBYjVsf8EVmi+GYpoaNhcj8Vu8AlUV1xG74 xwY4XgXI7mBo42ThRuNldJDCdYPh6wWlTmiXnE41qDd9C1BPHgZ4w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrgedtgdegvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpehfhffvufffjgfkgggtsehttdertddttddtnecuhfhrohhmpeflihhmucfvuhhr nhgvrhcuoehlihhnuhigkhgvrhhnvghlrdhfohhsshesughmrghrtgdqnhhonhgvrdhtuh hrnhgvrhdrlhhinhhkqeenucggtffrrghtthgvrhhnpeetheegvdetueefudelffejieff feetuefhveffveffffffhffguddtleehueevleenucffohhmrghinhepsghoohhtlhhinh drtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhm pehlihhnuhigkhgvrhhnvghlrdhfohhsshesughmrghrtgdqnhhonhgvrdhtuhhrnhgvrh drlhhinhhk X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 30 Jan 2022 21:16:21 -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> <87ee4wprsx.fsf@turner.link> <4b3ed7f6-d2b6-443c-970e-d963066ebfe3@amd.com> From: Jim 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: Sat, 29 Jan 2022 19:25:07 -0500 In-reply-to: <4b3ed7f6-d2b6-443c-970e-d963066ebfe3@amd.com> Message-ID: <87pmo8r6ob.fsf@turner.link> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? James