From: Andi Shyti <andi.shyti@linux.intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>,
Lucas De Marchi <lucas.demarchi@intel.com>,
DRI Devel <dri-devel@lists.freedesktop.org>,
Chris Wilson <chris@chris-wilson.co.uk>,
Matthew Auld <matthew.auld@intel.com>
Subject: Re: [Intel-gfx] [PATCH v5 5/7] drm/i915/gt: Create per-tile RC6 sysfs interface
Date: Fri, 18 Feb 2022 10:21:26 +0100 [thread overview]
Message-ID: <Yg9lFn2SFR4WwmOV@intel.intel> (raw)
In-Reply-To: <57edfc5a-a330-8661-1509-b375f67b495e@linux.intel.com>
Hi Tvrtko,
> > > > Now tiles have their own sysfs interfaces under the gt/
> > > > directory. Because RC6 is a property that can be configured on a
> > > > tile basis, then each tile should have its own interface
> > > >
> > > > The new sysfs structure will have a similar layout for the 4 tile
> > > > case:
> > > >
> > > > /sys/.../card0
> > > > ├── gt
> > > > │ ├── gt0
> > > > │ │ ├── id
> > > > │ │ ├── rc6_enable
> > > > │ │ ├── rc6_residency_ms
> > > > . . .
> > > > . . .
> > > > . .
> > > > │ └── gtN
> > > > │ ├── id
> > > > │ ├── rc6_enable
> > > > │ ├── rc6_residency_ms
> > > > │ .
> > > > │ .
> > > > │
> > > > └── power/ -+
> > > > ├── rc6_enable | Original interface
> > > > ├── rc6_residency_ms +-> kept as existing ABI;
> > > > . | it multiplexes over
> > > > . | the GTs
> > > > -+
> > > >
> > > > The existing interfaces have been kept in their original location
> > > > to preserve the existing ABI. They act on all the GTs: when
> > > > reading they provide the average value from all the GTs.
> > >
> > > Average feels very odd to me. I'd ask if we can get away providing an errno
> > > instead? Or tile zero data?
> >
> > Real multiplexing would be providing something when reading and
> > when writing. The idea of average came while revieweing with
> > Chris the write multiplexing. Indeed it makes sense to provide
> > some common value, but I don't know how useful it can be to the
> > user (still if the user needs any average).
> >
> > Joonas, Chris... any idea?
> >
> > > Case in point, and please correct me if I am wrong, legacy rc6_enable
> > > returns tile zero, while residency returns average.
> >
> > As the interface is done now, the rc6_enable is just returning
> > whether the gpu (i.e. i915, not gt) supports RC6 or not. I think
> > there is a patch later.
> >
> > > Even the deprecated message gets logged with every access right?
> > >
> > > Btw is the deperecated message limited to multi-tile platforms (can't see
> > > that it is) and what is the plan for that?
> >
> > yes, at this point the message would need to be removed and I
> > forgot to do it.
>
> Maybe it is correct to have it, I don't know at this point. Is the plan to
> remove the warning everywhere, or only have it on multi-tile platforms, or
> new platforms? And/or remove legacy files after a while on all platforms, or
> just new ones?
At this point I guess the warning should be removed from
everywhere (i.e. only those RC6 and RPS interfaces that are
duplicated/multiplexed).
We shouldn't be supposed to need more usage of multiplexed
interfaces in the future (maybe just rc6 enable, but I don't see
it really necessary).
Thanks,
Andi
WARNING: multiple messages have this Message-ID (diff)
From: Andi Shyti <andi.shyti@linux.intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>,
Lucas De Marchi <lucas.demarchi@intel.com>,
DRI Devel <dri-devel@lists.freedesktop.org>,
Chris Wilson <chris@chris-wilson.co.uk>,
Matthew Auld <matthew.auld@intel.com>,
Andi Shyti <andi.shyti@linux.intel.com>
Subject: Re: [Intel-gfx] [PATCH v5 5/7] drm/i915/gt: Create per-tile RC6 sysfs interface
Date: Fri, 18 Feb 2022 10:21:26 +0100 [thread overview]
Message-ID: <Yg9lFn2SFR4WwmOV@intel.intel> (raw)
In-Reply-To: <57edfc5a-a330-8661-1509-b375f67b495e@linux.intel.com>
Hi Tvrtko,
> > > > Now tiles have their own sysfs interfaces under the gt/
> > > > directory. Because RC6 is a property that can be configured on a
> > > > tile basis, then each tile should have its own interface
> > > >
> > > > The new sysfs structure will have a similar layout for the 4 tile
> > > > case:
> > > >
> > > > /sys/.../card0
> > > > ├── gt
> > > > │ ├── gt0
> > > > │ │ ├── id
> > > > │ │ ├── rc6_enable
> > > > │ │ ├── rc6_residency_ms
> > > > . . .
> > > > . . .
> > > > . .
> > > > │ └── gtN
> > > > │ ├── id
> > > > │ ├── rc6_enable
> > > > │ ├── rc6_residency_ms
> > > > │ .
> > > > │ .
> > > > │
> > > > └── power/ -+
> > > > ├── rc6_enable | Original interface
> > > > ├── rc6_residency_ms +-> kept as existing ABI;
> > > > . | it multiplexes over
> > > > . | the GTs
> > > > -+
> > > >
> > > > The existing interfaces have been kept in their original location
> > > > to preserve the existing ABI. They act on all the GTs: when
> > > > reading they provide the average value from all the GTs.
> > >
> > > Average feels very odd to me. I'd ask if we can get away providing an errno
> > > instead? Or tile zero data?
> >
> > Real multiplexing would be providing something when reading and
> > when writing. The idea of average came while revieweing with
> > Chris the write multiplexing. Indeed it makes sense to provide
> > some common value, but I don't know how useful it can be to the
> > user (still if the user needs any average).
> >
> > Joonas, Chris... any idea?
> >
> > > Case in point, and please correct me if I am wrong, legacy rc6_enable
> > > returns tile zero, while residency returns average.
> >
> > As the interface is done now, the rc6_enable is just returning
> > whether the gpu (i.e. i915, not gt) supports RC6 or not. I think
> > there is a patch later.
> >
> > > Even the deprecated message gets logged with every access right?
> > >
> > > Btw is the deperecated message limited to multi-tile platforms (can't see
> > > that it is) and what is the plan for that?
> >
> > yes, at this point the message would need to be removed and I
> > forgot to do it.
>
> Maybe it is correct to have it, I don't know at this point. Is the plan to
> remove the warning everywhere, or only have it on multi-tile platforms, or
> new platforms? And/or remove legacy files after a while on all platforms, or
> just new ones?
At this point I guess the warning should be removed from
everywhere (i.e. only those RC6 and RPS interfaces that are
duplicated/multiplexed).
We shouldn't be supposed to need more usage of multiplexed
interfaces in the future (maybe just rc6 enable, but I don't see
it really necessary).
Thanks,
Andi
next prev parent reply other threads:[~2022-02-18 9:21 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 14:41 [Intel-gfx] [PATCH v5 0/7] Introduce multitile support Andi Shyti
2022-02-17 14:41 ` Andi Shyti
2022-02-17 14:41 ` [Intel-gfx] [PATCH v5 1/7] drm/i915: Rename INTEL_REGION_LMEM with INTEL_REGION_LMEM_0 Andi Shyti
2022-02-17 14:41 ` Andi Shyti
2022-02-28 19:53 ` [Intel-gfx] " Michal Wajdeczko
2022-02-28 19:53 ` Michal Wajdeczko
2022-03-01 15:19 ` [Intel-gfx] " Andrzej Hajda
2022-03-01 15:19 ` Andrzej Hajda
2022-02-17 14:41 ` [Intel-gfx] [PATCH v5 2/7] drm/i915: Prepare for multiple GTs Andi Shyti
2022-02-17 14:41 ` Andi Shyti
2022-03-01 15:15 ` [Intel-gfx] " Andrzej Hajda
2022-03-01 15:15 ` Andrzej Hajda
2022-03-06 19:20 ` [Intel-gfx] " Andi Shyti
2022-03-06 19:20 ` Andi Shyti
2022-02-17 14:41 ` [Intel-gfx] [PATCH v5 3/7] drm/i915/gt: add gt_is_root() helper Andi Shyti
2022-02-17 14:41 ` Andi Shyti
2022-02-28 20:02 ` [Intel-gfx] " Michal Wajdeczko
2022-03-01 15:25 ` Andrzej Hajda
2022-03-06 19:23 ` Andi Shyti
2022-03-06 19:23 ` Andi Shyti
2022-02-17 14:41 ` [Intel-gfx] [PATCH v5 4/7] drm/i915/gt: create per-tile sysfs interface Andi Shyti
2022-02-17 14:41 ` Andi Shyti
2022-03-02 16:57 ` [Intel-gfx] " Andrzej Hajda
2022-03-02 16:57 ` Andrzej Hajda
2022-03-06 23:04 ` [Intel-gfx] " Andi Shyti
2022-03-06 23:04 ` Andi Shyti
2022-03-07 20:25 ` [Intel-gfx] " Andrzej Hajda
2022-03-07 20:25 ` Andrzej Hajda
2022-03-13 19:45 ` [Intel-gfx] " Andi Shyti
2022-03-13 19:45 ` Andi Shyti
2022-03-13 21:30 ` [Intel-gfx] " Andi Shyti
2022-03-13 21:30 ` Andi Shyti
2022-03-14 12:08 ` [Intel-gfx] " Andrzej Hajda
2022-03-14 12:08 ` Andrzej Hajda
2022-02-17 14:41 ` [Intel-gfx] [PATCH v5 5/7] drm/i915/gt: Create per-tile RC6 " Andi Shyti
2022-02-17 14:41 ` Andi Shyti
2022-02-17 15:34 ` [Intel-gfx] " Tvrtko Ursulin
2022-02-17 15:53 ` Andi Shyti
2022-02-17 15:53 ` Andi Shyti
2022-02-18 9:12 ` Tvrtko Ursulin
2022-02-18 9:21 ` Andi Shyti [this message]
2022-02-18 9:21 ` Andi Shyti
2022-02-18 10:46 ` Joonas Lahtinen
2022-02-21 17:12 ` Tvrtko Ursulin
2022-02-22 8:57 ` Andi Shyti
2022-02-22 8:57 ` Andi Shyti
2022-11-07 0:08 ` Dixit, Ashutosh
2022-11-07 0:08 ` Dixit, Ashutosh
2022-02-17 20:49 ` kernel test robot
2022-02-17 20:49 ` kernel test robot
2022-02-17 23:53 ` kernel test robot
2022-02-17 23:53 ` kernel test robot
2022-02-17 23:53 ` kernel test robot
2022-03-03 10:19 ` Andrzej Hajda
2022-03-03 10:19 ` Andrzej Hajda
2022-03-13 22:15 ` [Intel-gfx] " Andi Shyti
2022-03-13 22:15 ` Andi Shyti
2022-02-17 14:41 ` [Intel-gfx] [PATCH v5 6/7] drm/i915/gt: Create per-tile RPS sysfs interfaces Andi Shyti
2022-02-17 14:41 ` Andi Shyti
2022-02-17 19:47 ` [Intel-gfx] " kernel test robot
2022-02-17 19:47 ` kernel test robot
2022-03-03 10:55 ` Andrzej Hajda
2022-03-03 10:55 ` Andrzej Hajda
2022-03-13 23:09 ` [Intel-gfx] " Andi Shyti
2022-03-13 23:09 ` Andi Shyti
2022-02-17 14:41 ` [Intel-gfx] [PATCH v5 7/7] drm/i915/gt: Adding new sysfs frequency attributes Andi Shyti
2022-02-17 14:41 ` Andi Shyti
2022-02-17 15:45 ` [Intel-gfx] " Andi Shyti
2022-02-17 15:45 ` Andi Shyti
2022-02-17 17:06 ` [Intel-gfx] " Sundaresan, Sujaritha
2022-02-17 17:06 ` Sundaresan, Sujaritha
2022-02-28 20:37 ` [Intel-gfx] " Michal Wajdeczko
2022-02-28 20:37 ` Michal Wajdeczko
2022-03-14 0:38 ` [Intel-gfx] " Andi Shyti
2022-03-14 0:38 ` Andi Shyti
2022-03-14 1:32 ` [Intel-gfx] " Sundaresan, Sujaritha
2022-03-14 1:32 ` Sundaresan, Sujaritha
2022-03-03 11:17 ` [Intel-gfx] " Andrzej Hajda
2022-03-03 11:17 ` Andrzej Hajda
2022-02-17 23:12 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Introduce multitile support Patchwork
2022-02-17 23:13 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-17 23:40 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-02-17 23:40 ` [Intel-gfx] ✗ Fi.CI.BUILD: warning " 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=Yg9lFn2SFR4WwmOV@intel.intel \
--to=andi.shyti@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.auld@intel.com \
--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 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.