From: Andi Shyti <andi@etezian.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gt: make a gt sysfs group and move power management files
Date: Sat, 8 Feb 2020 19:01:53 +0200 [thread overview]
Message-ID: <20200208170153.GB32188@jack.zhora.eu> (raw)
In-Reply-To: <158118102661.18291.13808402197936060238@skylake-alporthouse-com>
Hi Chris,
> > > > The GT has its own properties and in sysfs they should be grouped
> > > > in the 'gt/' directory.
> > > >
> > > > Create the 'gt/' directory in sysfs and move the power management
> > > > related files.
> > >
> > > As shown by BAT, we have a conundrum; do we have to preserve the old
> > > names forevermore? Or do we just userspace that they have to adapt?
> >
> > With this, I guess you are suggesting to change igt accordingly,
> > because I'm pretty sure this interface is subject to change,
> > sooner or later.
>
> Right; but what about powertop? And the bajillion wikis?
mmhhh... right!
> Just feels clumsy, so I'd like to spend a moment to see if we can think
> of any options before dropping them. No matter how silly, if userspace
> breaks, it's a regression :(
>
> Maybe we could do something like keep the old ones and put a deprecation
> warning in?
how about linking and declare the old interface obsolete?
Andi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-02-08 17:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-08 12:27 [Intel-gfx] [PATCH] drm/i915/gt: make a gt sysfs group and move power management files Andi Shyti
2020-02-08 15:15 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-02-08 15:16 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2020-02-08 15:48 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-02-08 16:26 ` [Intel-gfx] [PATCH] " Chris Wilson
2020-02-08 16:51 ` Andi Shyti
2020-02-08 16:57 ` Chris Wilson
2020-02-08 17:01 ` Andi Shyti [this message]
2020-02-08 17:06 ` Chris Wilson
2020-02-08 17:23 ` Andi Shyti
2020-02-09 15:45 ` Jani Nikula
2020-02-09 15:50 ` Andi Shyti
2020-02-14 11:03 Andi Shyti
2020-02-14 12:54 ` Tvrtko Ursulin
2020-02-14 13:16 ` Andi Shyti
2020-02-14 13:38 ` Tvrtko Ursulin
2020-02-14 13:57 ` Andi Shyti
2020-02-14 13:18 ` Chris Wilson
2020-02-14 13:41 ` Tvrtko Ursulin
2020-02-14 13:14 ` Chris Wilson
2021-10-14 0:08 Andi Shyti
2021-10-14 23:51 ` Sundaresan, Sujaritha
2021-10-17 20:48 ` Andi Shyti
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=20200208170153.GB32188@jack.zhora.eu \
--to=andi@etezian.org \
--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;
as well as URLs for NNTP newsgroup(s).