From: Matthew Brost <matthew.brost@intel.com>
To: <intel-gfx@lists.freedesktop.org>, <dri-devel@lists.freedesktop.org>
Subject: [Intel-gfx] [PATCH 0/2] A few CT updates
Date: Thu, 20 Jan 2022 10:36:53 -0800 [thread overview]
Message-ID: <20220120183655.3228-1-matthew.brost@intel.com> (raw)
A couple of minor CT updates. 1 for performance, 1 for extra debug.
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
Matthew Brost (2):
drm/i915/guc: Don't check CT descriptor status before CT write / read
drm/i915/guc: Print CT descriptor status in CT debug function
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c | 10 ++++++++++
1 file changed, 10 insertions(+)
--
2.34.1
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Brost <matthew.brost@intel.com>
To: <intel-gfx@lists.freedesktop.org>, <dri-devel@lists.freedesktop.org>
Cc: daniele.ceraolospurio@intel.com, john.c.harrison@intel.com,
michal.wajdeczko@intel.com
Subject: [PATCH 0/2] A few CT updates
Date: Thu, 20 Jan 2022 10:36:53 -0800 [thread overview]
Message-ID: <20220120183655.3228-1-matthew.brost@intel.com> (raw)
A couple of minor CT updates. 1 for performance, 1 for extra debug.
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
Matthew Brost (2):
drm/i915/guc: Don't check CT descriptor status before CT write / read
drm/i915/guc: Print CT descriptor status in CT debug function
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c | 10 ++++++++++
1 file changed, 10 insertions(+)
--
2.34.1
next reply other threads:[~2022-01-20 18:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 18:36 Matthew Brost [this message]
2022-01-20 18:36 ` [PATCH 0/2] A few CT updates Matthew Brost
2022-01-20 18:36 ` [Intel-gfx] [PATCH 1/2] drm/i915/guc: Don't check CT descriptor status before CT write / read Matthew Brost
2022-01-20 18:36 ` Matthew Brost
2022-01-21 7:28 ` [Intel-gfx] " Jani Nikula
2022-01-21 7:28 ` Jani Nikula
2022-01-21 21:03 ` [Intel-gfx] " Matthew Brost
2022-01-21 21:03 ` Matthew Brost
2022-01-24 13:07 ` [Intel-gfx] " Jani Nikula
2022-01-24 13:07 ` Jani Nikula
2022-01-20 18:36 ` [Intel-gfx] [PATCH 2/2] drm/i915/guc: Print CT descriptor status in CT debug function Matthew Brost
2022-01-20 18:36 ` Matthew Brost
2022-01-20 21:15 ` [Intel-gfx] ✓ Fi.CI.BAT: success for A few CT updates Patchwork
2022-01-21 0:02 ` [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=20220120183655.3228-1-matthew.brost@intel.com \
--to=matthew.brost@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@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 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.