From: Lucas De Marchi <lucas.demarchi@intel.com>
To: Francois Dugast <francois.dugast@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
Jonathan Cavitt <jonathan.cavitt@intel.com>,
Robert Krzemien <robert.krzemien@intel.com>,
Matt Roper <matthew.d.roper@intel.com>,
Zhanjun Dong <zhanjun.dong@intel.com>
Subject: Re: [PATCH v4 2/2] drm/xe/uapi: Add L3 bank mask to topology query
Date: Fri, 22 Mar 2024 11:21:05 -0500 [thread overview]
Message-ID: <azsoakv3xpzq7ogbilm3dohpymt6qu5mlojksk37indq6bht4x@fd2ws5gqu2sl> (raw)
In-Reply-To: <20240321142521.7-2-francois.dugast@intel.com>
On Thu, Mar 21, 2024 at 02:25:21PM +0000, Francois Dugast wrote:
>Extend the existing topology uAPI to expose the masks of L3 banks
>to user space. L3 count is not sufficient because in some configuration
>not all banks are enabled. User space needs to know which ones are
>enabled, in the context of OA.
can we exand on *why* it needs to know the L3 bank configuration?
and since this is an uapi addition, please point out to the userspace
consumer.
Lucas De Marchi
next prev parent reply other threads:[~2024-03-22 16:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 14:25 [PATCH v4 1/2] drm/xe/query: Define and use a constant for the number of masks Francois Dugast
2024-03-21 14:25 ` [PATCH v4 2/2] drm/xe/uapi: Add L3 bank mask to topology query Francois Dugast
2024-03-22 16:21 ` Lucas De Marchi [this message]
2024-03-21 15:28 ` ✓ CI.Patch_applied: success for series starting with [v4,1/2] drm/xe/query: Define and use a constant for the number of masks Patchwork
2024-03-21 15:29 ` ✗ CI.checkpatch: warning " Patchwork
2024-03-21 15:30 ` ✓ CI.KUnit: success " Patchwork
2024-03-21 15:41 ` ✓ CI.Build: " Patchwork
2024-03-21 15:45 ` ✗ CI.Hooks: failure " Patchwork
2024-03-21 15:46 ` ✓ CI.checksparse: success " Patchwork
2024-03-21 16:09 ` ✓ CI.BAT: " 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=azsoakv3xpzq7ogbilm3dohpymt6qu5mlojksk37indq6bht4x@fd2ws5gqu2sl \
--to=lucas.demarchi@intel.com \
--cc=francois.dugast@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=robert.krzemien@intel.com \
--cc=zhanjun.dong@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.