Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@kernel.org>
Cc: "Upadhyay, Tejas" <tejas.upadhyay@intel.com>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"Vivi,  Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [Intel-xe] [PATCH 3/3] drm/xe: Add sysfs entry to report per gt memory size
Date: Fri, 05 May 2023 11:03:46 -0700	[thread overview]
Message-ID: <87lei2y7st.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <ZFUVYY7vFBBsYDWr@rdvivi-mobl4>

On Fri, 05 May 2023 07:40:33 -0700, Rodrigo Vivi wrote:
>
> > > > @@ -50,9 +114,15 @@ int xe_gt_sysfs_init(struct xe_gt *gt)
> > > >
> > > >		gt->sysfs = &kg->base;
> > > >
> > > > +	gt->sysfs_defaults = kobject_create_and_add(".defaults", gt->sysfs);
> > >
> > > what is the use of defaults??
> >
> > No use. There is no use I saw in i915 as well. But may be for some
> > future use it is kept. Or I missed something. If want to remove, can be
> > removed on objections.
>
> Cc: Ashutosh
>
> The defaults is used in i915 so Level-0/Sysman can perform the
> restore_defaults operation.
>
> I believe it is a useful feature...

Yeah for RW sysfs attributes, i915 had the convention of exposing default
values in /sys/class/.../.defaults (look at intel_gt_sysfs.c and
sysfs_engines.c) so userland can restore default values if sysfs attributes
had been previously modified. Level 0 was doing this in some cases.

For xe, we can do the same or something different I guess.

Also, are we going to re-create sysfs as done in this series or use
something like hwmon (it was being debated)?

Thanks.
--
Ashutosh

  reply	other threads:[~2023-05-05 18:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04 11:20 [Intel-xe] [PATCH 0/3] drm/xe: Add sysfs entry to report per gt memory size Tejas Upadhyay
2023-05-04 11:18 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-05-04 11:19 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-05-04 11:20 ` [Intel-xe] [PATCH 1/3] drm/xe: Rework multi tile device memory initialization Tejas Upadhyay
2023-05-04 11:20 ` [Intel-xe] [PATCH 2/3] drm/xe: Register drm device prior to gt init Tejas Upadhyay
2023-05-04 12:03   ` Iddamsetty, Aravind
2023-05-04 12:17     ` Upadhyay, Tejas
2023-05-04 11:20 ` [Intel-xe] [PATCH 3/3] drm/xe: Add sysfs entry to report per gt memory size Tejas Upadhyay
2023-05-04 12:43   ` Iddamsetty, Aravind
2023-05-04 12:50     ` Upadhyay, Tejas
2023-05-05 14:40       ` Rodrigo Vivi
2023-05-05 18:03         ` Dixit, Ashutosh [this message]
2023-05-08 10:44           ` Upadhyay, Tejas
2023-05-04 11:23 ` [Intel-xe] ✓ CI.Build: success for " Patchwork
2023-05-04 12:04 ` [Intel-xe] [PATCH 0/3] " Iddamsetty, Aravind
2023-05-04 12:15   ` Upadhyay, Tejas
2023-05-29  8:39 ` Upadhyay, Tejas
2023-05-29  8:45   ` Iddamsetty, Aravind
2023-05-30  6:51     ` Iddamsetty, Aravind
2023-05-30  9:31       ` Upadhyay, Tejas
2023-06-02  6:51       ` Upadhyay, Tejas
2023-06-02 15:17         ` Matt Roper
2023-06-05  6:08           ` Upadhyay, Tejas
2023-06-05 13:38           ` Upadhyay, Tejas
2023-06-06 21:46             ` Matt Roper

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=87lei2y7st.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=rodrigo.vivi@kernel.org \
    --cc=tejas.upadhyay@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