From: "Lazar, Lijo" <lijo.lazar@amd.com>
To: James Turner <linuxkernel.foss@dmarc-none.turner.link>
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
"Pan, Xinhui" <Xinhui.Pan@amd.com>,
LKML <linux-kernel@vger.kernel.org>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
Alex Williamson <alex.williamson@redhat.com>,
Thorsten Leemhuis <regressions@leemhuis.info>,
Alex Deucher <alexdeucher@gmail.com>,
"Koenig, Christian" <Christian.Koenig@amd.com>
Subject: Re: [REGRESSION] Too-low frequency limit for AMD GPU PCI-passed-through to Windows VM
Date: Tue, 25 Jan 2022 19:03:52 +0530 [thread overview]
Message-ID: <4b3ed7f6-d2b6-443c-970e-d963066ebfe3@amd.com> (raw)
In-Reply-To: <87ee4wprsx.fsf@turner.link>
On 1/25/2022 5:28 AM, James Turner wrote:
> 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
>
>
Hi James,
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
The patch specifically affects these two. On/before starting VM, if
there are invocations of these two functions on your system as a result
of the patch, we could navigate from there and check what is the side
effect.
Thanks,
Lijo
> 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
>
WARNING: multiple messages have this Message-ID (diff)
From: "Lazar, Lijo" <lijo.lazar@amd.com>
To: James Turner <linuxkernel.foss@dmarc-none.turner.link>
Cc: Alex Deucher <alexdeucher@gmail.com>,
Thorsten Leemhuis <regressions@leemhuis.info>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
"Pan, Xinhui" <Xinhui.Pan@amd.com>,
LKML <linux-kernel@vger.kernel.org>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
Alex Williamson <alex.williamson@redhat.com>,
"Koenig, Christian" <Christian.Koenig@amd.com>
Subject: Re: [REGRESSION] Too-low frequency limit for AMD GPU PCI-passed-through to Windows VM
Date: Tue, 25 Jan 2022 19:03:52 +0530 [thread overview]
Message-ID: <4b3ed7f6-d2b6-443c-970e-d963066ebfe3@amd.com> (raw)
In-Reply-To: <87ee4wprsx.fsf@turner.link>
On 1/25/2022 5:28 AM, James Turner wrote:
> 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
>
>
Hi James,
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
The patch specifically affects these two. On/before starting VM, if
there are invocations of these two functions on your system as a result
of the patch, we could navigate from there and check what is the side
effect.
Thanks,
Lijo
> 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
>
next prev parent reply other threads:[~2022-01-25 13:34 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 2:12 [REGRESSION] Too-low frequency limit for AMD GPU PCI-passed-through to Windows VM James D. Turner
2022-01-17 8:09 ` Greg KH
2022-01-17 9:03 ` Thorsten Leemhuis
2022-01-18 3:14 ` James Turner
2022-01-21 2:13 ` James Turner
2022-01-21 6:22 ` Thorsten Leemhuis
2022-01-21 6:22 ` Thorsten Leemhuis
2022-01-21 16:45 ` Alex Deucher
2022-01-21 16:45 ` Alex Deucher
2022-01-22 0:51 ` James Turner
2022-01-22 0:51 ` James Turner
2022-01-22 5:52 ` Lazar, Lijo
2022-01-22 5:52 ` Lazar, Lijo
2022-01-22 21:11 ` James Turner
2022-01-22 21:11 ` James Turner
2022-01-24 14:21 ` Lazar, Lijo
2022-01-24 14:21 ` Lazar, Lijo
2022-01-24 23:58 ` James Turner
2022-01-24 23:58 ` James Turner
2022-01-25 13:33 ` Lazar, Lijo [this message]
2022-01-25 13:33 ` Lazar, Lijo
2022-01-30 0:25 ` Jim Turner
2022-01-30 0:25 ` Jim Turner
2022-02-15 14:56 ` Thorsten Leemhuis
2022-02-15 14:56 ` Thorsten Leemhuis
2022-02-15 15:11 ` Alex Deucher
2022-02-15 15:11 ` Alex Deucher
2022-02-16 0:25 ` James D. Turner
2022-02-16 0:25 ` James D. Turner
2022-02-16 16:37 ` Alex Deucher
2022-02-16 16:37 ` Alex Deucher
2022-03-06 15:48 ` Thorsten Leemhuis
2022-03-06 15:48 ` Thorsten Leemhuis
2022-03-07 2:12 ` James Turner
2022-03-07 2:12 ` James Turner
2022-03-13 18:33 ` James Turner
2022-03-13 18:33 ` James Turner
2022-03-17 12:54 ` Thorsten Leemhuis
2022-03-17 12:54 ` Thorsten Leemhuis
2022-03-18 5:43 ` Paul Menzel
2022-03-18 5:43 ` Paul Menzel
2022-03-18 7:01 ` Thorsten Leemhuis
2022-03-18 7:01 ` Thorsten Leemhuis
2022-03-18 14:46 ` Alex Williamson
2022-03-18 14:46 ` Alex Williamson
2022-03-18 15:06 ` Alex Deucher
2022-03-18 15:06 ` Alex Deucher
2022-03-18 15:25 ` Alex Williamson
2022-03-18 15:25 ` Alex Williamson
2022-03-21 1:26 ` James Turner
2022-03-21 1:26 ` James Turner
2022-01-24 17:04 ` Alex Deucher
2022-01-24 17:04 ` Alex Deucher
2022-01-24 17:30 ` Alex Williamson
2022-01-24 17:30 ` Alex Williamson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4b3ed7f6-d2b6-443c-970e-d963066ebfe3@amd.com \
--to=lijo.lazar@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=alex.williamson@redhat.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxkernel.foss@dmarc-none.turner.link \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.