From: James Zhu <jamesz@amd.com>
To: Zhu Lingshan <lingshan.zhu@amd.com>,
Alexander.Deucher@amd.com, felix.kuehling@amd.com
Cc: Ray.Huang@amd.com, amd-gfx@lists.freedesktop.org
Subject: Re: [RFC 02/10] drm/amdgpu: add device-wide PMC config
Date: Wed, 23 Sep 2026 10:13:01 -0400 [thread overview]
Message-ID: <d3144b38-64a3-4bbe-910f-722912f9fc66@amd.com> (raw)
In-Reply-To: <20260922093436.596947-3-lingshan.zhu@amd.com>
On 2026-09-22 05:34, Zhu Lingshan wrote:
> This commit implements a device-wide PMC config
> for amdgpu, which including the profiling owner,
> and the profiling enablement indicator.
[JZ] I think it should be render-node wide, not device-wide
>
> Signed-off-by: Zhu Lingshan <lingshan.zhu@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu.h | 8 ++++++++
> drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 3 +++
> 2 files changed, 11 insertions(+)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu.h b/drivers/gpu/drm/amd/amdgpu/amdgpu.h
> index 8eff6b9ebe81..45897dca802f 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu.h
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu.h
> @@ -620,6 +620,12 @@ enum amdgpu_enforce_isolation_mode {
> AMDGPU_ENFORCE_ISOLATION_NO_CLEANER_SHADER = 3,
> };
>
> +struct amdgpu_pmc_profiler {
> + struct mutex lock;
> + struct drm_file *owner;
> + bool enable;
> +};
> +
> struct amdgpu_device {
> struct device *dev;
> struct pci_dev *pdev;
> @@ -818,6 +824,8 @@ struct amdgpu_device {
> */
> struct xarray userq_doorbell_xa;
>
> + struct amdgpu_pmc_profiler pmc_profiler;
> +
> /* df */
> struct amdgpu_df df;
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> index c924a55fd16f..74ed42e53264 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> @@ -3673,6 +3673,7 @@ int amdgpu_device_init(struct amdgpu_device *adev,
> mutex_init(&adev->pm.stable_pstate_ctx_lock);
> mutex_init(&adev->benchmark_mutex);
> mutex_init(&adev->gfx.reset_sem_mutex);
> + mutex_init(&adev->pmc_profiler.lock);
>
> /* Associate locks with lockdep classes for ordering validation */
> amdgpu_lockdep_set_class(adev);
> @@ -4244,6 +4245,8 @@ void amdgpu_device_fini_sw(struct amdgpu_device *adev)
> kfree(adev->pci_state);
> kfree(adev->pcie_reset_ctx.swds_pcistate);
> kfree(adev->pcie_reset_ctx.swus_pcistate);
> +
> + mutex_destroy(&adev->pmc_profiler.lock);
> }
>
> /**
next prev parent reply other threads:[~2026-09-23 14:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 9:34 [RFC 00/10] amdgpu: implement Performance Monitor Counter support Zhu Lingshan
2026-09-22 9:34 ` [RFC 01/10] drm/amdgpu: implement PMC ioctl framework Zhu Lingshan
2026-09-23 14:17 ` James Zhu
2026-09-24 3:38 ` Zhu, Lingshan
2026-09-24 15:49 ` James Zhu
2026-10-08 7:59 ` Zhu, Lingshan
2026-09-22 9:34 ` [RFC 02/10] drm/amdgpu: add device-wide PMC config Zhu Lingshan
2026-09-23 14:13 ` James Zhu [this message]
2026-09-24 3:23 ` Zhu, Lingshan
2026-09-24 15:40 ` James Zhu
2026-10-08 7:50 ` Zhu, Lingshan
2026-09-22 9:34 ` [RFC 03/10] drm/amdgpu: introduce PMC ioctl handler Zhu Lingshan
2026-09-22 9:34 ` [RFC 04/10] drm/amdgpu: implement reservation mechanism for PMC Zhu Lingshan
2026-09-22 9:34 ` [RFC 05/10] drm/amdgpu: set device-wide PMC enablement indicator Zhu Lingshan
2026-09-22 9:34 ` [RFC 06/10] drm/amdgpu: GFX11: set mqd->perfcount from mqd_prop Zhu Lingshan
2026-09-22 9:34 ` [RFC 07/10] drm/amdgpu: GFX12: " Zhu Lingshan
2026-09-22 9:34 ` [RFC 08/10] drm/amdgpu: GFX12.1: " Zhu Lingshan
2026-09-22 9:34 ` [RFC 09/10] drm/amdgpu: implement device PMC handler Zhu Lingshan
2026-09-22 9:34 ` [RFC 10/10] drm/amdgpu: set userq perf state before publish it Zhu Lingshan
2026-09-23 14:02 ` [RFC 00/10] amdgpu: implement Performance Monitor Counter support James Zhu
2026-09-23 15:02 ` Welton, Benjamin
2026-09-23 15:11 ` James Zhu
2026-09-24 3:40 ` Zhu, Lingshan
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=d3144b38-64a3-4bbe-910f-722912f9fc66@amd.com \
--to=jamesz@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Ray.Huang@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=felix.kuehling@amd.com \
--cc=lingshan.zhu@amd.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox