From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915/params: add i915 parameters to debugfs
Date: Wed, 15 Jan 2020 15:12:59 +0200 [thread overview]
Message-ID: <87imlckgmc.fsf@intel.com> (raw)
In-Reply-To: <87sgkhj96b.fsf@intel.com>
On Wed, 15 Jan 2020, Jani Nikula <jani.nikula@intel.com> wrote:
> On Wed, 15 Jan 2020, Chris Wilson <chris@chris-wilson.co.uk> wrote:
>> Quoting Jani Nikula (2019-12-05 15:43:40)
>>> Add a debugfs subdirectory i915_params with all the i915 module
>>> parameters. This is a first step, with lots of boilerplate, and not much
>>> benefit yet.
>>
>> Right, creates a mirror [more or less] of /sys/module/i915/parameters. I
>> probably would have used parameters/ rather than i915_params/, but that
>> is immaterial.
>
> I guess I used i915_ because it's sort of a shared namespace with drm
> core, which in itself is, IMO, a historical mistake. Perhaps there
> should've been a driver/ debugfs directory for driver specific debug
> files.
>
> What if someone wanted to add a drm core level parameters/ file or
> directory? Would be kind of embarrassing to say, don't do that, i915
> already uses it...
>
>>>
>>> This will result in a new device specific debugfs directory at
>>> /sys/kernel/debug/dri/<N>/i915_params duplicating the module specific
>>> sysfs directory at /sys/module/i915/parameters/. Going forward, all
>>> users of the parameters should use the debugfs, with the module
>>> parameters being phased out.
>>>
>>> Add debugfs permissions to I915_PARAMS_FOR_EACH(). This duplicates the
>>> mode with module parameter sysfs, but the goal is to make the module
>>> parameters read-only initial values for device specific parameters.
>>>
>>> 0 mode will bypass debugfs creation. Use it for verbose_state_checks
>>> which will need special attention in follow-up work.
>>
>> The patch does what you say, hopefully a local entropy maxima.
>> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
>
> Many thanks,
> Jani.
And pushed both to dinq, thanks again for the review.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-01-15 13:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 15:43 [Intel-gfx] [PATCH 0/2] drm/i915: debugfs device parameters Jani Nikula
2019-12-05 15:43 ` [Intel-gfx] [PATCH 1/2] drm/i915/params: add i915 parameters to debugfs Jani Nikula
2019-12-05 17:19 ` Tvrtko Ursulin
2019-12-09 9:53 ` Jani Nikula
2020-01-08 14:45 ` Chris Wilson
2020-01-08 15:07 ` Jani Nikula
2020-01-15 10:04 ` Chris Wilson
2020-01-15 10:39 ` Jani Nikula
2020-01-15 13:12 ` Jani Nikula [this message]
2019-12-05 15:43 ` [Intel-gfx] [PATCH 2/2] drm/i915/params: support bool values for int and uint params Jani Nikula
2020-01-15 10:05 ` Chris Wilson
2019-12-05 17:24 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: debugfs device parameters Patchwork
2019-12-05 17:26 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2019-12-05 17:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2019-12-05 23:06 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
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=87imlckgmc.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@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