Nouveau Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Simon Ser <contact@emersion.fr>, "Nieto, David M" <David.Nieto@amd.com>
Cc: "nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
	Intel Graphics Development <Intel-gfx@lists.freedesktop.org>,
	Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
	Daniel Vetter <daniel@ffwll.ch>,
	"Koenig, Christian" <Christian.Koenig@amd.com>
Subject: Re: [Nouveau] [PATCH 0/7] Per client engine busyness
Date: Tue, 18 May 2021 10:08:59 +0100	[thread overview]
Message-ID: <7f8fc38a-cd25-aa1f-fa2d-5d3334edb3d2@linux.intel.com> (raw)
In-Reply-To: <mysJHURIfWxBRBabIlnunj7LZNkkRQ-Knu_o6v7GZI4xCwGMZXn0rvjscl-aTT_d-ttlAQgJOG3gP95DBd_dxCPQNfguTSdrltxPrKt2FGs=@emersion.fr>


On 17/05/2021 20:03, Simon Ser wrote:
> On Monday, May 17th, 2021 at 8:16 PM, Nieto, David M <David.Nieto@amd.com> wrote:
> 
>> Btw is DRM_MAJOR 226 consider uapi? I don't see it in uapi headers.
> 
> It's not in the headers, but it's de facto uAPI, as seen in libdrm:
> 
>      > git grep 226
>      xf86drm.c
>      99:#define DRM_MAJOR 226 /* Linux */

I suspected it would be yes, thanks.

I was just wondering if stat(2) and a chrdev major check would be a 
solid criteria to more efficiently (compared to parsing the text 
content) detect drm files while walking procfs.

Regards,

Tvrtko
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  reply	other threads:[~2021-05-18  9:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c6c61179-5b4b-4e0b-6e57-ec4839ca3268@linux.intel.com>
     [not found] ` <CADnq5_N03pz6GmptzhRnCRQH=qkd4eWuAbuUysHp-A9NZHQMHg@mail.gmail.com>
     [not found]   ` <BYAPR12MB2840AA68BCAEBD9279C6184FF4509@BYAPR12MB2840.namprd12.prod.outlook.com>
     [not found]     ` <39ccc2ef-05d1-d9f0-0639-ea86bef58b80@amd.com>
     [not found]       ` <7d6d09fe-ec85-6aaf-9834-37a49ec7d6c5@linux.intel.com>
     [not found]         ` <9144f63b-953d-2019-742d-6553e09f5b40@amd.com>
     [not found]           ` <22e7d6ea-f2dd-26da-f264-b17aad25af95@linux.intel.com>
     [not found]             ` <b2203d34-2de3-7c58-de2f-bf6fafc3f67c@amd.com>
     [not found]               ` <6cf2f14a-6a16-5ea3-d307-004faad4cc79@linux.intel.com>
     [not found]                 ` <a2b03603-eb3e-7bef-a799-c15cfb1a8e0b@amd.com>
     [not found]                   ` <YKJ+F4KqEiQQYkRz@phenom.ffwll.local>
     [not found]                     ` <BYAPR12MB2840C633CF05C1F29263F5BCF42D9@BYAPR12MB2840.namprd12.prod.outlook.com>
     [not found]                       ` <c85fc53f-d25b-464c-d411-eed4a509a009@linux.intel.com>
     [not found]                         ` <BYAPR12MB28409E25DEFD3DD620E596ABF42D9@BYAPR12MB2840.namprd12.prod.outlook.com>
2021-05-17 18:16                           ` [Nouveau] [PATCH 0/7] Per client engine busyness Nieto, David M
2021-05-17 19:03                             ` Simon Ser
2021-05-18  9:08                               ` Tvrtko Ursulin [this message]
2021-05-18  9:16                                 ` Daniel Stone
2021-05-18  9:40                                   ` Tvrtko Ursulin
2021-05-19 16:16                                     ` Tvrtko Ursulin
2021-05-19 18:23                                       ` [Nouveau] [Intel-gfx] " Daniel Vetter
2021-05-19 23:17                                         ` Nieto, David M
2021-05-20 14:11                                           ` Daniel Vetter
2021-05-20 14:12                                             ` Christian König
2021-05-20 14:17                                               ` arabek
2021-05-20  8:35                                         ` Tvrtko Ursulin
2021-05-24 10:48                                           ` Tvrtko Ursulin

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=7f8fc38a-cd25-aa1f-fa2d-5d3334edb3d2@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=Christian.Koenig@amd.com \
    --cc=David.Nieto@amd.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=contact@emersion.fr \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=nouveau@lists.freedesktop.org \
    /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