public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Venkata Sandeep Dhanalakota <venkata.s.dhanalakota@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, chris.p.wilson@intel.com
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915/perf: Register sysctl path globally
Date: Wed, 11 Dec 2019 09:13:18 -0800	[thread overview]
Message-ID: <20191211171318.GE47225@intel.com> (raw)
In-Reply-To: <96a54ef7-86d2-0e9b-e0bc-20878883cfea@linux.intel.com>

On 19/12/11 04:39, Tvrtko Ursulin wrote:
> 
> On 11/12/2019 16:31, Tvrtko Ursulin wrote:
> > On 11/12/2019 16:07, Venkata Sandeep Dhanalakota wrote:
> > > We do not require to register the sysctl paths per instance,
> > > so making registration global.
> > > 
> > > Cc: Sudeep Dutt <sudeep.dutt@intel.com>
> > > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > > Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> > > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > > Cc: Jani Nikula <jani.nikula@intel.com>
> > > Signed-off-by: Venkata Sandeep Dhanalakota
> > > <venkata.s.dhanalakota@intel.com>
> > > ---
> > >   drivers/gpu/drm/i915/i915_perf.c       | 10 ++++++++--
> > >   drivers/gpu/drm/i915/i915_perf_types.h |  1 -
> > >   2 files changed, 8 insertions(+), 3 deletions(-)
> > > 
> > > diff --git a/drivers/gpu/drm/i915/i915_perf.c
> > > b/drivers/gpu/drm/i915/i915_perf.c
> > > index 8d2e37949f46..426d04214a5d 100644
> > > --- a/drivers/gpu/drm/i915/i915_perf.c
> > > +++ b/drivers/gpu/drm/i915/i915_perf.c
> > > @@ -387,6 +387,8 @@ struct i915_oa_config_bo {
> > >       struct i915_vma *vma;
> > >   };
> > > +static struct ctl_table_header *sysctl_header;
> > > +
> > >   static enum hrtimer_restart oa_poll_check_timer_cb(struct hrtimer
> > > *hrtimer);
> > >   void i915_oa_config_release(struct kref *ref)
> > > @@ -4345,7 +4347,8 @@ void i915_perf_init(struct drm_i915_private *i915)
> > >           oa_sample_rate_hard_limit = 1000 *
> > >               (RUNTIME_INFO(i915)->cs_timestamp_frequency_khz / 2);
> > > -        perf->sysctl_header = register_sysctl_table(dev_root);
> > > +        if (!sysctl_header)
> > > +            sysctl_header = register_sysctl_table(dev_root);
> > >           mutex_init(&perf->metrics_lock);
> > >           idr_init(&perf->metrics_idr);
> > > @@ -4395,7 +4398,10 @@ void i915_perf_fini(struct drm_i915_private *i915)
> > >       idr_for_each(&perf->metrics_idr, destroy_config, perf);
> > >       idr_destroy(&perf->metrics_idr);
> > > -    unregister_sysctl_table(perf->sysctl_header);
> > > +    if (sysctl_header) {
> > > +        unregister_sysctl_table(sysctl_header);
> > > +        sysctl_header = NULL;
> > > +    }
> > 
> > I am not sure if this could be racy with manual unbind from sysfs. Does
> > PCI core serialize for us?
> 
> Actually with two devices you also need to reference count it since you
> don't want removal of the first device to remove the node but last.
> 
Apparently this is not called during module exit, using krefs is
way go to or have some helper which are called during module init/exit.

void i915_perf_sysctl_register() {
	sysctl_header = register_sysctl_table(dev_root);
}

void i915_perf_sysctl_unregister() {
	unregister_sysctl_table(sysctl_header);
}


> > Regards,
> > 
> > Tvrtko
> > 
> > >       memset(&perf->ops, 0, sizeof(perf->ops));
> > >       perf->i915 = NULL;
> > > diff --git a/drivers/gpu/drm/i915/i915_perf_types.h
> > > b/drivers/gpu/drm/i915/i915_perf_types.h
> > > index 74ddc20a0d37..45e581455f5d 100644
> > > --- a/drivers/gpu/drm/i915/i915_perf_types.h
> > > +++ b/drivers/gpu/drm/i915/i915_perf_types.h
> > > @@ -380,7 +380,6 @@ struct i915_perf {
> > >       struct drm_i915_private *i915;
> > >       struct kobject *metrics_kobj;
> > > -    struct ctl_table_header *sysctl_header;
> > >       /*
> > >        * Lock associated with adding/modifying/removing OA configs
> > > 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-12-11 17:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 16:07 [Intel-gfx] [PATCH 1/2] drm/i915/perf: Register sysctl path globally Venkata Sandeep Dhanalakota
2019-12-11 16:07 ` [Intel-gfx] [PATCH 2/2] drm/i915: Make warned variable private Venkata Sandeep Dhanalakota
2019-12-11 16:17   ` Chris Wilson
2019-12-11 16:19     ` Chris Wilson
2019-12-11 22:20       ` Lucas De Marchi
2019-12-11 22:22         ` Chris Wilson
2019-12-11 16:13 ` [Intel-gfx] [PATCH 1/2] drm/i915/perf: Register sysctl path globally Lionel Landwerlin
2019-12-11 16:31 ` Tvrtko Ursulin
2019-12-11 16:39   ` Tvrtko Ursulin
2019-12-11 17:13     ` Venkata Sandeep Dhanalakota [this message]
2019-12-11 17:25       ` Tvrtko Ursulin
2019-12-11 22:14       ` Lucas De Marchi
2019-12-11 22:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] " Patchwork
2019-12-12  9:08 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2019-12-12  7:35 [Intel-gfx] [PATCH 1/2] " Venkata Sandeep Dhanalakota
2019-12-12 21:34 ` Lucas De Marchi
2019-12-13  5:07   ` Venkata Sandeep Dhanalakota
2019-12-13  9:12 Venkata Sandeep Dhanalakota
2019-12-13 15:51 Venkata Sandeep Dhanalakota
2019-12-13 16:09 ` Chris Wilson
2019-12-13 17:41   ` Lucas De Marchi
2019-12-13 20:02 Venkata Sandeep Dhanalakota
2019-12-16 10:27 ` Jani Nikula
2019-12-16 11:23   ` Chris Wilson

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=20191211171318.GE47225@intel.com \
    --to=venkata.s.dhanalakota@intel.com \
    --cc=chris.p.wilson@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=tvrtko.ursulin@linux.intel.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