From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Ayaz A Siddiqui <ayaz.siddiqui@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 0/1] lib/rendercopy_gen9: Program platform specific MOCS index
Date: Mon, 16 Aug 2021 19:56:03 +0300 [thread overview]
Message-ID: <YRqYoyZYLCVn4K9+@intel.com> (raw)
In-Reply-To: <20210803110934.970874-1-ayaz.siddiqui@intel.com>
On Tue, Aug 03, 2021 at 04:39:33PM +0530, Ayaz A Siddiqui wrote:
> Since Gen12 onward PTE based catchability is not supported to changing
> PTE index to UC as safest catchability.
That doesn't make any sense to me. Without a PTE MOCS setting all
buffers that have the potential of becoming scanout buffers will
have to be UC, which doesn't sound particularly great.
Also we do have the PTE MOCS index still programmed on gen12 AFAICS.
>
> Based on further need, we may move intel_get_uc_mocs() in some common file,
> so that it can be useed for providing uc index for other modules also.
>
>
> Ayaz A Siddiqui (1):
> lib/rendercopy_gen9: Program MOCS value based on platform
>
> lib/rendercopy_gen9.c | 33 ++++++++++++++++++++++++++++++++-
> 1 file changed, 32 insertions(+), 1 deletion(-)
>
> --
> 2.26.2
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2021-08-16 16:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 11:09 [igt-dev] [PATCH i-g-t 0/1] lib/rendercopy_gen9: Program platform specific MOCS index Ayaz A Siddiqui
2021-08-03 11:09 ` [igt-dev] [PATCH i-g-t 1/1] lib/rendercopy_gen9: Program MOCS value based on platform Ayaz A Siddiqui
2021-08-06 11:12 ` Kahola, Mika
2021-08-03 11:59 ` [igt-dev] ✓ Fi.CI.BAT: success for lib/rendercopy_gen9: Program platform specific MOCS index Patchwork
2021-08-03 23:53 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2021-08-16 16:56 ` Ville Syrjälä [this message]
2021-08-16 17:25 ` [igt-dev] [PATCH i-g-t 0/1] " Siddiqui, Ayaz A
2021-08-16 17:44 ` Ville Syrjälä
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=YRqYoyZYLCVn4K9+@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=ayaz.siddiqui@intel.com \
--cc=igt-dev@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