Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: "Ghimiray, Himal Prasad" <himal.prasad.ghimiray@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 1/1] drm/i915: Export LMEM max memory bandwidth via sysfs
Date: Tue, 22 Nov 2022 21:59:25 -0800	[thread overview]
Message-ID: <87r0xuw6rm.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <MWHPR11MB146920C662B733EE935D73BAB30C9@MWHPR11MB1469.namprd11.prod.outlook.com>

On Tue, 22 Nov 2022 21:10:01 -0800, Ghimiray, Himal Prasad wrote:
>
> > -----Original Message-----
> > From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> > Sent: 21 November 2022 17:17
> > To: Ghimiray, Himal Prasad <himal.prasad.ghimiray@intel.com>; intel-
> > gfx@lists.freedesktop.org
> > Subject: Re: [Intel-gfx] [PATCH 1/1] drm/i915: Export LMEM max memory
> > bandwidth via sysfs
> >
> >
> > On 21/11/2022 10:01, Himal Prasad Ghimiray wrote:
> > > Export lmem maximum memory bandwidth to the userspace via sysfs
> > >
> > > (v2)
> > > Add TODO comment to have client parts specific condition (Anshuman)
> > > Remove prelim prefix from the sysfs node name (Aravind)
> >
> > Link to userspace consumer?
> [Ghimiray, Himal Prasad]
>
> Does above comment means stating name of sysfs node in commit message ?

No. It means that there has to be a "real" open source userspace program
(like Mesa, Level-0/OneApi or another accepted program or UMD) which is
actually reading the sysfs file exposed. Without such a consumer, the sysfs
addition will not be accepted upstream.

E.g. see cover letter here:

https://patchwork.freedesktop.org/series/106460/

"An approved Level-0/oneAPI UMD pull request which consumes the exposed
defaults can be seen here:
	https://github.com/intel/compute-runtime/pull/552
"

Thanks.
--
Ashutosh

  reply	other threads:[~2022-11-23  5:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-21 10:01 [Intel-gfx] [PATCH 1/1] drm/i915: Export LMEM max memory bandwidth via sysfs Himal Prasad Ghimiray
2022-11-21 11:29 ` Gupta, Anshuman
2022-11-23  5:04   ` Ghimiray, Himal Prasad
2022-11-21 11:47 ` Tvrtko Ursulin
2022-11-23  5:10   ` Ghimiray, Himal Prasad
2022-11-23  5:59     ` Dixit, Ashutosh [this message]
2022-11-23  6:01       ` Ghimiray, Himal Prasad
2022-11-21 12:17 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for series starting with [1/1] " Patchwork
2022-11-21 12:37 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-11-21 15:20 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2022-11-15  8:08 [Intel-gfx] [PATCH 1/1] " Himal Prasad Ghimiray
2022-11-16  9:39 ` Iddamsetty, Aravind
2022-11-16 10:08 ` Gupta, Anshuman
2022-11-16 10:48   ` Ghimiray, Himal Prasad
2022-11-21  6:49     ` Ghimiray, Himal Prasad

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=87r0xuw6rm.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=himal.prasad.ghimiray@intel.com \
    --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