All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marek Olšák" <maraeo@gmail.com>
To: "Quan, Evan" <Evan.Quan@amd.com>
Cc: "Michel Dänzer" <michel@daenzer.net>,
	"Christian König" <ckoenig.leichtzumerken@gmail.com>,
	"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: Sat, 18 Sep 2021 03:19:38 -0400	[thread overview]
Message-ID: <CAAxE2A7RL+LEgwtQwH2s9_Zm5FZFKvGYpRqTZzxiXAwXdaeR6w@mail.gmail.com> (raw)
In-Reply-To: <DM6PR12MB261970C1F0CDB0D1D91EE7C9E4DD9@DM6PR12MB2619.namprd12.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2680 bytes --]

Hi,

Printing the backtrace from si_flush_gfx_cs while /etc/environment contains
GALLIUM_THREAD=0 at boot should show which GL call and X call caused the
flush.

Marek

On Thu, Sep 16, 2021 at 10:58 PM Quan, Evan <Evan.Quan@amd.com> wrote:

> [Public]
>
>
>
> > -----Original Message-----
> > From: Michel Dänzer <michel@daenzer.net>
> > Sent: Thursday, September 16, 2021 4:12 PM
> > 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
> >
> > 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.
> >
> Thanks for sharing these.
> >
> > 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.
> >
> Got it. Thanks!
>
> Evan
> >
> > --
> > Earthling Michel Dänzer               |
> > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fredh
> > at.com%2F&amp;data=04%7C01%7CEvan.Quan%40amd.com%7C296d316427
> > b4469f8eb908d978e9b46a%7C3dd8961fe4884e608e11a82d994e183d%7C0%7
> > C0%7C637673767426116632%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4w
> > LjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&am
> > p;sdata=gBj4idZGCuaPdyaH1g1mfuDqPCcKhFMjPCbqpM8drlg%3D&amp;res
> > erved=0
> > Libre software enthusiast             |             Mesa and X developer
>

[-- Attachment #2: Type: text/html, Size: 4298 bytes --]

  reply	other threads:[~2021-09-18  7:20 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
2021-09-17  2:58     ` Quan, Evan
2021-09-18  7:19       ` Marek Olšák [this message]
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=CAAxE2A7RL+LEgwtQwH2s9_Zm5FZFKvGYpRqTZzxiXAwXdaeR6w@mail.gmail.com \
    --to=maraeo@gmail.com \
    --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 \
    --cc=michel@daenzer.net \
    /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.