From: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Upadhyay, Tejas" <tejas.upadhyay@intel.com>,
"aravind.iddamsetty@linux.intel.com"
<aravind.iddamsetty@linux.intel.com>
Cc: "Roper, Matthew D" <matthew.d.roper@intel.com>
Subject: Re: [PATCH] drm/xe: Remove vram size info from sysfs
Date: Wed, 13 Dec 2023 15:53:06 +0000 [thread overview]
Message-ID: <5403be007f18a7df3e3dacb283794a4fb60185e0.camel@intel.com> (raw)
In-Reply-To: <ca95972f-2d5d-4fc6-bca3-e80f984e79cf@linux.intel.com>
On Wed, 2023-12-13 at 10:48 +0530, Aravind Iddamsetty wrote:
>
> On 12/13/23 09:43, Upadhyay, Tejas wrote:
> >
> > > -----Original Message-----
> > > From: Intel-xe <intel-xe-bounces@lists.freedesktop.org> On Behalf
> > > Of Rodrigo
> > > Vivi
> > > Sent: Tuesday, December 12, 2023 5:51 AM
> > > To: intel-xe@lists.freedesktop.org
> > > Cc: Roper, Matthew D <matthew.d.roper@intel.com>; Vivi, Rodrigo
> > > <rodrigo.vivi@intel.com>
> > > Subject: [PATCH] drm/xe: Remove vram size info from sysfs
> > >
> > > This information is already part of the query IOCTL.
> > > Let's not duplicate it here in the sysfs.
> > This patch was on request from L0 as they wanted actual VRAM size
> > including reserved portion. We should check with UMD team if they
> > require this sysfs or not. I will check.
>
> Hi Rodrigo,
>
> As Tejas mentioned the sysfs interface exposes the total physical
> vram including the stolen size which is needed by sysman, in the
> IOCTL only usable size(without stolen) is exposed.
I have removed it now so we can discuss better and ensure that we
are taking the best uapi decisions that are acceptable and won't
break the compatibility later after we are merged upstream.
The time to break was now, so I removed.
But we can continue with the discussion and see what is the best
approach.
My first question would be: why does Level0 needs to know the stolen
size? So, why we don't add that information along with the query uapi?
It would be really awkward to see a value in the sysfs as total memory
and a completely different value on the query ioclt? this stolen part
apparently needs to be more transparent then, no?!
>
>
> Thanks,
> Aravind.
> >
> > Tejas
> > > Cc: Matt Roper <matthew.d.roper@intel.com>
> > > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > > ---
> > > drivers/gpu/drm/xe/xe_tile_sysfs.c | 23 +----------------------
> > > 1 file changed, 1 insertion(+), 22 deletions(-)
> > >
> > > diff --git a/drivers/gpu/drm/xe/xe_tile_sysfs.c
> > > b/drivers/gpu/drm/xe/xe_tile_sysfs.c
> > > index 16376607c68f..0f8d3e7fce46 100644
> > > --- a/drivers/gpu/drm/xe/xe_tile_sysfs.c
> > > +++ b/drivers/gpu/drm/xe/xe_tile_sysfs.c
> > > @@ -20,20 +20,6 @@ static const struct kobj_type
> > > xe_tile_sysfs_kobj_type = {
> > > .sysfs_ops = &kobj_sysfs_ops,
> > > };
> > >
> > > -static ssize_t
> > > -physical_vram_size_bytes_show(struct device *kdev, struct
> > > device_attribute
> > > *attr,
> > > - char *buf)
> > > -{
> > > - struct xe_tile *tile = kobj_to_tile(&kdev->kobj);
> > > -
> > > - return sysfs_emit(buf, "%llu\n", tile-
> > > >mem.vram.actual_physical_size);
> > > -}
> > > -
> > > -static DEVICE_ATTR_RO(physical_vram_size_bytes);
> > > -
> > > -static const struct attribute *physical_memsize_attr =
> > > - &dev_attr_physical_vram_size_bytes.attr;
> > > -
> > > static void tile_sysfs_fini(struct drm_device *drm, void *arg)
> > > {
> > > struct xe_tile *tile = arg;
> > > @@ -64,15 +50,8 @@ void xe_tile_sysfs_init(struct xe_tile *tile)
> > >
> > > tile->sysfs = &kt->base;
> > >
> > > - if (IS_DGFX(xe) && xe->info.platform != XE_DG1 &&
> > > - sysfs_create_file(tile->sysfs,
> > > physical_memsize_attr))
> > > - drm_warn(&xe->drm,
> > > - "Sysfs creation to read addr_range per
> > > tile failed\n");
> > > -
> > > err = drmm_add_action_or_reset(&xe->drm, tile_sysfs_fini,
> > > tile);
> > > - if (err) {
> > > + if (err)
> > > drm_warn(&xe->drm, "%s: drmm_add_action_or_reset
> > > failed, err: %d\n",
> > > __func__, err);
> > > - return;
> > > - }
> > > }
> > > --
> > > 2.43.0
next prev parent reply other threads:[~2023-12-13 15:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 0:20 [PATCH] drm/xe: Remove vram size info from sysfs Rodrigo Vivi
2023-12-12 2:08 ` ✓ CI.Patch_applied: success for " Patchwork
2023-12-12 2:09 ` ✓ CI.checkpatch: " Patchwork
2023-12-12 2:10 ` ✓ CI.KUnit: " Patchwork
2023-12-12 2:17 ` ✓ CI.Build: " Patchwork
2023-12-12 2:17 ` ✓ CI.Hooks: " Patchwork
2023-12-12 2:19 ` ✓ CI.checksparse: " Patchwork
2023-12-12 2:54 ` ✓ CI.BAT: " Patchwork
2023-12-12 17:35 ` [PATCH] " Matt Roper
2023-12-13 4:13 ` Upadhyay, Tejas
2023-12-13 5:18 ` Aravind Iddamsetty
2023-12-13 15:53 ` Vivi, Rodrigo [this message]
2023-12-14 5:52 ` Aravind Iddamsetty
2023-12-14 9:43 ` Matthew Auld
2023-12-14 11:20 ` Aravind Iddamsetty
2023-12-15 2:20 ` Upadhyay, Tejas
2023-12-15 3:57 ` Aravind Iddamsetty
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=5403be007f18a7df3e3dacb283794a4fb60185e0.camel@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=aravind.iddamsetty@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@intel.com \
--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