From: "Michel Dänzer" <michel@daenzer.net>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
"Quan, Evan" <Evan.Quan@amd.com>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
"Koenig, Christian" <Christian.Koenig@amd.com>,
"'amd-gfx@lists.freedesktop.org'" <amd-gfx@lists.freedesktop.org>
Subject: Re: DRM IOCTLS come regularly(every minute) still even after screen off
Date: Thu, 16 Sep 2021 10:12:17 +0200 [thread overview]
Message-ID: <d8293063-6f0e-b808-2636-631fe2f08fcf@daenzer.net> (raw)
In-Reply-To: <4ded93f1-e6b1-06c3-9f03-b6135911392c@gmail.com>
On 2021-09-16 08:27, Christian König wrote:
> Good morning,
>
> for the background I advised to contact you Michel since we couldn't find an explanation.
>
> Alex explanation might be correct, but the CS seems to come from the X server and is always roughly 60 seconds after going into power save.
>
> Any idea what that could be?
For the DRM_IOCTL_MODE_* ioctls, attaching gdb to Xorg and setting a breakpoint on drmIoctl should show where they're coming from.
The AMDGPU_CS ioctls are probably from glamor calling OpenGL, most likely for X11 drawing protocol requests. Note that in this case drmIoctl/ioctl will likely be called from a separate thread. Pierre / Marek should be able to help you find out where the OpenGL calls are coming from.
In general, Xorg only ever does anything in response to:
* X11 protocol requests, i.e. on behalf of clients.
* Input events, i.e. on behalf of the user.
* Other kernel events, e.g. hotplug events.
FWIW, with only xfwm4 & xterm running on Xorg, I'm not seeing any drmIoctl calls during DPMS off. So the ioctls you're seeing are most likely triggered by clients.
--
Earthling Michel Dänzer | https://redhat.com
Libre software enthusiast | Mesa and X developer
next prev parent reply other threads:[~2021-09-16 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 3:15 DRM IOCTLS come regularly(every minute) still even after screen off Quan, Evan
2021-09-16 6:27 ` Christian König
2021-09-16 8:12 ` Michel Dänzer [this message]
2021-09-17 2:58 ` Quan, Evan
2021-09-18 7:19 ` Marek Olšák
2021-09-18 9:16 ` Michel Dänzer
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=d8293063-6f0e-b808-2636-631fe2f08fcf@daenzer.net \
--to=michel@daenzer.net \
--cc=Alexander.Deucher@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=Evan.Quan@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=ckoenig.leichtzumerken@gmail.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 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.