All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas De Marchi <lucas.demarchi@intel.com>
To: Tejas Upadhyay <tejaskumarx.surendrakumar.upadhyay@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH V2] drm/i915/ehl: Update MOCS table for EHL
Date: Tue, 29 Jun 2021 18:02:02 -0700	[thread overview]
Message-ID: <20210630010202.ewlpgzxtvezbivpb@ldmartin-desk2> (raw)
In-Reply-To: <20210621125622.877864-1-tejaskumarx.surendrakumar.upadhyay@intel.com>

On Mon, Jun 21, 2021 at 06:26:22PM +0530, Tejas Upadhyay wrote:
>From: Matt Roper <matthew.d.roper@intel.com>
>
>These extra EHL entries were not behaving as expected without proper
>flushing implemented in kernel.
>Commit a679f58d0510 ("drm/i915: Flush pages on acquisition")
>introduces proper flushing to make it work as expected.
>
>Hence adding those EHL entries back.
>
>Changes since V1:
>	- commit message modified with Commit - Joonas
>
>Cc: Francisco Jerez <francisco.jerez.plata@intel.com>
>Cc: Jon Bloomfield <jon.bloomfield@intel.com>
>Cc: Lucas De Marchi <lucas.demarchi@intel.com>
>Cc: <stable@vger.kernel.org>
>Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
>Fixes: 046091758b50 ("Revert "drm/i915/ehl: Update MOCS table for EHL"")

This story here is weird as we reverted something going to
v5.4 due to something missing, but that something was already in the
tree since v5.1. So it seems the revert shouldn't had been done in the
first place? What am I reading wrong here?

For any gt/gem patches, we need to Cc dri-devel, done now.

Also, it seems your client is suppressing the Cc you added in the body,
so you are actually not sending anything to stable, or to the people
added there.


>Link: https://patchwork.freedesktop.org/patch/msgid/20191112224757.25116-1-matthew.d.roper@intel.com
>---
> drivers/gpu/drm/i915/gt/intel_mocs.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
>diff --git a/drivers/gpu/drm/i915/gt/intel_mocs.c b/drivers/gpu/drm/i915/gt/intel_mocs.c
>index 17848807f111..7d9ef0210805 100644
>--- a/drivers/gpu/drm/i915/gt/intel_mocs.c
>+++ b/drivers/gpu/drm/i915/gt/intel_mocs.c
>@@ -194,6 +194,14 @@ static const struct drm_i915_mocs_entry broxton_mocs_table[] = {
> 	MOCS_ENTRY(15, \
> 		   LE_3_WB | LE_TC_1_LLC | LE_LRUM(2) | LE_AOM(1), \
> 		   L3_3_WB), \
>+	/* Bypass LLC - Uncached (EHL+) */ \
>+	MOCS_ENTRY(16, \
>+		   LE_1_UC | LE_TC_1_LLC | LE_SCF(1), \
>+		   L3_1_UC), \
>+	/* Bypass LLC - L3 (Read-Only) (EHL+) */ \
>+	MOCS_ENTRY(17, \
>+		   LE_1_UC | LE_TC_1_LLC | LE_SCF(1), \
>+		   L3_3_WB), \

For the change itself: it matches bspec 34007.

Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>

Lucas De Marchi

> 	/* Self-Snoop - L3 + LLC */ \
> 	MOCS_ENTRY(18, \
> 		   LE_3_WB | LE_TC_1_LLC | LE_LRUM(3) | LE_SSE(3), \
>-- 
>2.31.1
>
>_______________________________________________
>Intel-gfx mailing list
>Intel-gfx@lists.freedesktop.org
>https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Lucas De Marchi <lucas.demarchi@intel.com>
To: Tejas Upadhyay <tejaskumarx.surendrakumar.upadhyay@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH V2] drm/i915/ehl: Update MOCS table for EHL
Date: Tue, 29 Jun 2021 18:02:02 -0700	[thread overview]
Message-ID: <20210630010202.ewlpgzxtvezbivpb@ldmartin-desk2> (raw)
In-Reply-To: <20210621125622.877864-1-tejaskumarx.surendrakumar.upadhyay@intel.com>

On Mon, Jun 21, 2021 at 06:26:22PM +0530, Tejas Upadhyay wrote:
>From: Matt Roper <matthew.d.roper@intel.com>
>
>These extra EHL entries were not behaving as expected without proper
>flushing implemented in kernel.
>Commit a679f58d0510 ("drm/i915: Flush pages on acquisition")
>introduces proper flushing to make it work as expected.
>
>Hence adding those EHL entries back.
>
>Changes since V1:
>	- commit message modified with Commit - Joonas
>
>Cc: Francisco Jerez <francisco.jerez.plata@intel.com>
>Cc: Jon Bloomfield <jon.bloomfield@intel.com>
>Cc: Lucas De Marchi <lucas.demarchi@intel.com>
>Cc: <stable@vger.kernel.org>
>Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
>Fixes: 046091758b50 ("Revert "drm/i915/ehl: Update MOCS table for EHL"")

This story here is weird as we reverted something going to
v5.4 due to something missing, but that something was already in the
tree since v5.1. So it seems the revert shouldn't had been done in the
first place? What am I reading wrong here?

For any gt/gem patches, we need to Cc dri-devel, done now.

Also, it seems your client is suppressing the Cc you added in the body,
so you are actually not sending anything to stable, or to the people
added there.


>Link: https://patchwork.freedesktop.org/patch/msgid/20191112224757.25116-1-matthew.d.roper@intel.com
>---
> drivers/gpu/drm/i915/gt/intel_mocs.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
>diff --git a/drivers/gpu/drm/i915/gt/intel_mocs.c b/drivers/gpu/drm/i915/gt/intel_mocs.c
>index 17848807f111..7d9ef0210805 100644
>--- a/drivers/gpu/drm/i915/gt/intel_mocs.c
>+++ b/drivers/gpu/drm/i915/gt/intel_mocs.c
>@@ -194,6 +194,14 @@ static const struct drm_i915_mocs_entry broxton_mocs_table[] = {
> 	MOCS_ENTRY(15, \
> 		   LE_3_WB | LE_TC_1_LLC | LE_LRUM(2) | LE_AOM(1), \
> 		   L3_3_WB), \
>+	/* Bypass LLC - Uncached (EHL+) */ \
>+	MOCS_ENTRY(16, \
>+		   LE_1_UC | LE_TC_1_LLC | LE_SCF(1), \
>+		   L3_1_UC), \
>+	/* Bypass LLC - L3 (Read-Only) (EHL+) */ \
>+	MOCS_ENTRY(17, \
>+		   LE_1_UC | LE_TC_1_LLC | LE_SCF(1), \
>+		   L3_3_WB), \

For the change itself: it matches bspec 34007.

Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>

Lucas De Marchi

> 	/* Self-Snoop - L3 + LLC */ \
> 	MOCS_ENTRY(18, \
> 		   LE_3_WB | LE_TC_1_LLC | LE_LRUM(3) | LE_SSE(3), \
>-- 
>2.31.1
>
>_______________________________________________
>Intel-gfx mailing list
>Intel-gfx@lists.freedesktop.org
>https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2021-06-30  1:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21 12:56 [Intel-gfx] [PATCH V2] drm/i915/ehl: Update MOCS table for EHL Tejas Upadhyay
2021-06-21 15:28 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/ehl: Update MOCS table for EHL (rev4) Patchwork
2021-06-21 17:54 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-06-30  1:02 ` Lucas De Marchi [this message]
2021-06-30  1:02   ` [Intel-gfx] [PATCH V2] drm/i915/ehl: Update MOCS table for EHL Lucas De Marchi

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=20210630010202.ewlpgzxtvezbivpb@ldmartin-desk2 \
    --to=lucas.demarchi@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=tejaskumarx.surendrakumar.upadhyay@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.