From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chuanxiao Dong <chuanxiao.dong@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: intel-gvt-dev@lists.freedesktop.org
Subject: Re: [PATCH v4] drm/i915/scheduler: add gvt notification for guc submission
Date: Mon, 27 Mar 2017 13:14:12 +0300 [thread overview]
Message-ID: <1490609652.3166.9.camel@linux.intel.com> (raw)
In-Reply-To: <1490320162-16521-1-git-send-email-chuanxiao.dong@intel.com>
On pe, 2017-03-24 at 09:49 +0800, Chuanxiao Dong wrote:
> GVT request needs a manual mmio load/restore. Before GuC submit
> a request, send notification to gvt for mmio loading. And after
> the GuC finished this GVT request, notify gvt again for mmio
> restore. This follows the usage when using execlists submission.
>
> v2: use context_status_change instead of execlists_context_status_change
> for better understanding (ZhengXiao)
> v3: remove the comment as it is obvious and not friendly to
> the caller (Kevin)
> v4: fix indent issues (Joonas)
> rename the context_status_change to intel_gvt_notify_context_status (Chris)
>
> Cc: xiao.zheng@intel.com
> Cc: kevin.tian@intel.com
> Cc: joonas.lahtinen@linux.intel.com
> Cc: chris@chris-wilson.co.uk
> Signed-off-by: Chuanxiao Dong <chuanxiao.dong@intel.com>
<SNIP>
> @@ -634,6 +636,8 @@ static void i915_guc_irq_handler(unsigned long data)
> rq = port[0].request;
> while (rq && i915_gem_request_completed(rq)) {
> trace_i915_gem_request_out(rq);
> + intel_gvt_notify_context_status(rq,
> + INTEL_CONTEXT_SCHEDULE_OUT);
Code indent is still broken.
> @@ -87,5 +87,19 @@ uint64_t intel_lr_context_descriptor(struct i915_gem_context *ctx,
> /* Execlists */
> int intel_sanitize_enable_execlists(struct drm_i915_private *dev_priv,
> int enable_execlists);
> +static inline void
> +intel_gvt_notify_context_status(struct drm_i915_gem_request *rq,
> + unsigned long status)
With that prefix, this needs to go to intel_gvt.h, where you can take
advantage of the existing #ifdef block (which should really be #if
IS_ENABLED() too).
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-03-27 10:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 1:48 [PATCH] drm/i915/scheduler: add gvt notification for guc submission Chuanxiao Dong
2017-03-20 2:46 ` Zheng, Xiao
2017-03-20 3:19 ` Dong, Chuanxiao
2017-03-21 1:38 ` Zheng, Xiao
2017-03-21 1:58 ` Dong, Chuanxiao
2017-03-21 2:38 ` [PATCH v2] " Chuanxiao Dong
2017-03-21 3:07 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-03-21 11:23 ` ✗ Fi.CI.BAT: failure " Patchwork
2017-03-22 6:34 ` [PATCH v3] " Chuanxiao Dong
2017-03-23 5:29 ` Dong, Chuanxiao
2017-03-23 7:58 ` Tian, Kevin
2017-03-23 9:37 ` Joonas Lahtinen
2017-03-23 9:42 ` Chris Wilson
2017-03-23 13:43 ` Dong, Chuanxiao
2017-03-23 13:43 ` Dong, Chuanxiao
2017-03-23 9:51 ` Tvrtko Ursulin
2017-03-23 13:51 ` Dong, Chuanxiao
2017-03-24 1:49 ` [PATCH v4] " Chuanxiao Dong
2017-03-27 2:35 ` Dong, Chuanxiao
2017-03-27 10:14 ` Joonas Lahtinen [this message]
2017-03-27 10:58 ` Dong, Chuanxiao
2017-03-27 11:43 ` Joonas Lahtinen
2017-03-27 13:32 ` [PATCH v5] " Chuanxiao Dong
2017-03-27 13:49 ` Chris Wilson
2017-03-27 14:22 ` Dong, Chuanxiao
2017-03-27 14:33 ` Chris Wilson
2017-03-27 14:39 ` Dong, Chuanxiao
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=1490609652.3166.9.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chuanxiao.dong@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-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;
as well as URLs for NNTP newsgroup(s).