From: Andi Shyti <andi.shyti@linux.intel.com>
To: "Zhang, Carl" <carl.zhang@intel.com>
Cc: "Gu, Lihao" <lihao.gu@intel.com>,
Intel GFX <intel-gfx@lists.freedesktop.org>,
DRI Devel <dri-devel@lists.freedesktop.org>,
Chris Wilson <chris@chris-wilson.co.uk>,
"Roper, Matthew D" <matthew.d.roper@intel.com>
Subject: Re: [Intel-gfx] [PATCH v17 1/1] drm/i915: Allow user to set cache at BO creation
Date: Wed, 7 Jun 2023 07:11:16 +0200 [thread overview]
Message-ID: <ZIARdL44LW5BEysa@ashyti-mobl2.lan> (raw)
In-Reply-To: <PH0PR11MB5579C119BEF9653A9A20CC4E8753A@PH0PR11MB5579.namprd11.prod.outlook.com>
Hi Carl,
On Wed, Jun 07, 2023 at 03:40:20AM +0000, Zhang, Carl wrote:
> Media driver reverted previous patches, and file a new PR
> https://github.com/intel/media-driver/pull/1680
> will hold this PR until the uapi changes appear in drm_next.
That's great, thanks a lot for the quick actions here.
Before pushing I am going to replace the Media part in the commit
log with the following sentence:
"
The media driver supprt has bin submitted in this merge request:
https://github.com/intel/media-driver/pull/1680
"
> besides this, ask a dumb question.
> How we retrieve the pat_index from a shared resource though dma_buf fd?
> maybe we need to know whether it could be CPU cached if we want map it.
> Of course, looks there are no real usage to access it though CPU.
> Just use it directly without any pat related options ?
I am not understanding. Do you want to ask the PAT table to the
driver? Are you referring to the CPU PAT index?
In any case, if I understood correctly, you don't necessarily
always need to set the PAT options and the cache options will
fall into the default values.
Please let me know if I haven't answered the question.
Andi
> Thanks
> Carl
>
> > -----Original Message-----
> > From: Andi Shyti <andi.shyti@linux.intel.com>
> > Sent: Tuesday, June 6, 2023 7:15 PM
> > To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> > Cc: Andi Shyti <andi.shyti@linux.intel.com>; Tvrtko Ursulin
> > <tvrtko.ursulin@linux.intel.com>; Yang, Fei <fei.yang@intel.com>; Chris
> > Wilson <chris@chris-wilson.co.uk>; Roper, Matthew D
> > <matthew.d.roper@intel.com>; Justen, Jordan L <jordan.l.justen@intel.com>;
> > Zhang, Carl <carl.zhang@intel.com>; Gu, Lihao <lihao.gu@intel.com>; Intel
> > GFX <intel-gfx@lists.freedesktop.org>; DRI Devel <dri-
> > devel@lists.freedesktop.org>
> > Subject: Re: [PATCH v17 1/1] drm/i915: Allow user to set cache at BO creation
> >
> > > > > > To comply with the design that buffer objects shall have
> > > > > > immutable cache setting through out their life cycle, {set,
> > > > > > get}_caching ioctl's are no longer supported from MTL onward.
> > > > > > With that change caching policy can only be set at object
> > > > > > creation time. The current code applies a default (platform dependent)
> > cache setting for all objects.
> > > > > > However this is not optimal for performance tuning. The patch
> > > > > > extends the existing gem_create uAPI to let user set PAT index
> > > > > > for the object at creation time.
> > > > > > The new extension is platform independent, so UMD's can switch
> > > > > > to using this extension for older platforms as well, while {set,
> > > > > > get}_caching are still supported on these legacy paltforms for
> > compatibility reason.
> > > > > > However, since PAT index was not clearly defined for platforms
> > > > > > prior to
> > > > > > GEN12 (TGL), so we are limiting this externsion to GEN12+
> > > > > > platforms only. See ext_set_pat() in for the implementation details.
> > > > > >
> > > > > > Note: The documentation related to the PAT/MOCS tables is
> > > > > > currently available for Tiger Lake here:
> > > > > > https://www.intel.com/content/www/us/en/docs/graphics-for-linux/
> > > > > > developer-reference/1-0/tiger-lake.html
> > > > > >
> > > > > > BSpec: 45101
> > > > > >
> > > > > > Mesa support has been submitted in this merge request:
> > > > > > https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/22878
> > > > > >
> > > > > > The media driver is supported by the following commits:
> > > > > > https://github.com/intel/media-
> > driver/commit/92c00a857433ebb34ec
> > > > > > 575e9834f473c6fcb6341
> > > > > > https://github.com/intel/media-driver/commit/fd375cf2c5e1f6bf6b4
> > > > > > 3258ff797b3134aadc9fd
> > > > > > https://github.com/intel/media-
> > driver/commit/08dd244b22484770a33
> > > > > > 464c2c8ae85430e548000
> > >
> > > Andi, let's still get these corrected before merging once the
> > > media-driver revert is completed.
> >
> > Sure!
> >
> > At least this doesn't need a new version to be respinned.
> >
> > Please, Carl, link the new pull request and I will update the commit log.
> >
> > Andi
next prev parent reply other threads:[~2023-06-07 5:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 10:00 [Intel-gfx] [PATCH v17 0/1] drm/i915: Allow user to set cache at BO creation Andi Shyti
2023-06-06 10:00 ` [Intel-gfx] [PATCH v17 1/1] " Andi Shyti
2023-06-06 10:10 ` Tvrtko Ursulin
2023-06-06 10:18 ` Andi Shyti
2023-06-06 11:12 ` Joonas Lahtinen
2023-06-06 11:14 ` Andi Shyti
2023-06-07 3:40 ` Zhang, Carl
2023-06-07 5:11 ` Andi Shyti [this message]
2023-06-07 5:21 ` Zhang, Carl
2023-06-09 9:59 ` Andi Shyti
2023-06-09 15:12 ` Yang, Fei
2023-06-11 14:43 ` Zhang, Carl
2023-06-07 15:01 ` Andi Shyti
2023-06-07 15:46 ` Andi Shyti
2023-06-06 14:47 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2023-06-06 14:47 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-06-06 14:57 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-06-07 3:23 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=ZIARdL44LW5BEysa@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=carl.zhang@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lihao.gu@intel.com \
--cc=matthew.d.roper@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