From: Matthew Brost <matthew.brost@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: <apoorva.singh@intel.com>, <intel-xe@lists.freedesktop.org>,
<oak.zeng@intel.com>, Brian Welty <brian.welty@intel.com>
Subject: Re: [PATCH 2/2] drm/xe/uapi: Restore uapi for access counting
Date: Wed, 2 Oct 2024 15:03:46 +0000 [thread overview]
Message-ID: <Zv1g0tKMaCZXMKs0@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <juv7n3jsyv6hqcxbcnlxgeq5rlqayukriwrcbjq3lmonlhrnos@t5dpzwna5r27>
On Tue, Oct 01, 2024 at 04:02:55PM -0500, Lucas De Marchi wrote:
> On Tue, Oct 01, 2024 at 07:24:32PM GMT, apoorva.singh@intel.com wrote:
> > From: Brian Welty <brian.welty@intel.com>
> >
> > In order to enable access counters, this must be enabled in LRC for
> > the exec_queue. Add basic uAPI to set configuration of access counter
> > trigger threshold and granularity.
> >
> > When access counters are enabled and threshold is hit, the access
> > counter handler in xe_gt_pagefault.c will migrate the buffer to that
> > to that GT's local VRAM.
> >
> > Signed-off-by: Brian Welty <brian.welty@intel.com>
> > Signed-off-by: Apoorva Singh <apoorva.singh@intel.com>
>
>
> What do you mean by **Restore**? I'd expect a minimum amount of
> documentation explaining what this is and how a real
> userspace can be used it for implementing X, Y and Z. Link to userspace
> is also missing, and is required for uapi.
>
I was going to say do we have user space for this yet? I also suspect
getting this implementation right is going to part of the SVM work. I
personally rather leave this disabled until we get the SVM
implementation for this all worked out so we can freely change this if
required.
I can't imagine any user space is really demanding this to be enabled
yet.
Matt
> Lucas De Marchi
next prev parent reply other threads:[~2024-10-02 15:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 13:54 [PATCH 0/2] drm/xe/uapi: Restore uapi for access counting apoorva.singh
2024-10-01 13:50 ` ✓ CI.Patch_applied: success for " Patchwork
2024-10-01 13:50 ` ✓ CI.checkpatch: " Patchwork
2024-10-01 13:51 ` ✓ CI.KUnit: " Patchwork
2024-10-01 13:54 ` [PATCH 1/2] drm/xe: Add support for PTE_NC bit apoorva.singh
2024-10-01 16:26 ` Cavitt, Jonathan
2024-10-01 13:54 ` [PATCH 2/2] drm/xe/uapi: Restore uapi for access counting apoorva.singh
2024-10-01 16:35 ` Cavitt, Jonathan
2024-10-01 21:02 ` Lucas De Marchi
2024-10-02 15:03 ` Matthew Brost [this message]
2024-10-02 17:42 ` Lucas De Marchi
2024-10-03 5:15 ` Dandamudi, Priyanka
2024-10-01 14:02 ` ✓ CI.Build: success for " Patchwork
2024-10-01 14:05 ` ✗ CI.Hooks: failure " Patchwork
2024-10-01 14:06 ` ✓ CI.checksparse: success " Patchwork
2024-10-01 14:25 ` ✗ CI.BAT: failure " Patchwork
2024-10-01 22:06 ` ✗ CI.FULL: " 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=Zv1g0tKMaCZXMKs0@DUT025-TGLU.fm.intel.com \
--to=matthew.brost@intel.com \
--cc=apoorva.singh@intel.com \
--cc=brian.welty@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=oak.zeng@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