From: Jeff McGee <jeff.mcgee@intel.com>
To: "Michał Winiarski" <michal.winiarski@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 03/10] drm/i915/guc: Add preemption action to GuC firmware interface
Date: Thu, 5 Oct 2017 07:25:23 -0700 [thread overview]
Message-ID: <20171005142523.GA2868@jeffdesk> (raw)
In-Reply-To: <20171005091349.9315-3-michal.winiarski@intel.com>
On Thu, Oct 05, 2017 at 11:13:42AM +0200, Michał Winiarski wrote:
> We're using GuC action to request preemption. However, after requesting
> preemption we need to wait for GuC to finish its own post-processing
> before we start submitting our requests. Firmware is using shared
> context to report its status.
> Let's update GuC firmware interface with those new definitions.
>
> Cc: Jeff Mcgee <jeff.mcgee@intel.com>
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Oscar Mateo <oscar.mateo@intel.com>
> Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>
Reviewed-by: Jeff McGee <jeff.mcgee@intel.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-10-05 14:30 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 9:13 [PATCH 01/10] drm/i915/guc: Precompute GuC shared data offset Michał Winiarski
2017-10-05 9:13 ` [PATCH 02/10] drm/i915/guc: Initialize GuC before restarting engines Michał Winiarski
2017-10-05 9:36 ` Chris Wilson
2017-10-05 11:55 ` Michał Winiarski
2017-10-05 9:13 ` [PATCH 03/10] drm/i915/guc: Add preemption action to GuC firmware interface Michał Winiarski
2017-10-05 14:25 ` Jeff McGee [this message]
2017-10-05 9:13 ` [PATCH 04/10] drm/i915/guc: Add a second client, to be used for preemption Michał Winiarski
2017-10-05 9:39 ` Chris Wilson
2017-10-05 13:59 ` Michal Wajdeczko
2017-10-05 14:58 ` Jeff McGee
2017-10-05 15:22 ` Daniele Ceraolo Spurio
2017-10-05 16:00 ` Michał Winiarski
2017-10-05 16:35 ` Daniele Ceraolo Spurio
2017-10-05 18:20 ` Michał Winiarski
2017-10-05 9:13 ` [PATCH 05/10] drm/i915/guc: Split guc_wq_item_append Michał Winiarski
2017-10-05 9:45 ` Chris Wilson
2017-10-05 20:37 ` Jeff McGee
2017-10-05 9:20 ` [PATCH 06/10] drm/i915: Extract "emit write" part of emit breadcrumb functions Michał Winiarski
2017-10-05 9:20 ` [PATCH 07/10] drm/i915: Add information needed to track engine preempt state Michał Winiarski
2017-10-05 9:49 ` Chris Wilson
2017-10-05 20:42 ` Jeff McGee
2017-10-05 9:20 ` [PATCH 08/10] drm/i915/guc: Keep request->priority for its lifetime Michał Winiarski
2017-10-05 9:50 ` Chris Wilson
2017-10-05 9:20 ` [PATCH 09/10] drm/i915/guc: Preemption! With GuC Michał Winiarski
2017-10-05 10:04 ` Chris Wilson
2017-10-05 10:31 ` Chris Wilson
2017-10-05 18:38 ` Michał Winiarski
2017-10-05 15:00 ` Michal Wajdeczko
2017-10-05 15:42 ` Michał Winiarski
2017-10-05 9:20 ` [PATCH 10/10] HAX Enable GuC Submission for CI Michał Winiarski
2017-10-05 9:47 ` [PATCH 06/10] drm/i915: Extract "emit write" part of emit breadcrumb functions Chris Wilson
2017-10-05 9:33 ` [PATCH 01/10] drm/i915/guc: Precompute GuC shared data offset Chris Wilson
2017-10-05 17:02 ` Daniele Ceraolo Spurio
2017-10-06 12:35 ` Michał Winiarski
2017-10-06 16:24 ` Daniele Ceraolo Spurio
2017-10-05 11:30 ` Michal Wajdeczko
2017-10-26 21:22 ` ✗ Fi.CI.BAT: failure for series starting with [01/10] " 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=20171005142523.GA2868@jeffdesk \
--to=jeff.mcgee@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.winiarski@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