All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michel Thierry <michel.thierry@intel.com>
To: "Wang, Zhi A" <zhi.a.wang@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Cc: "He, Min" <min.he@intel.com>,
	"Li, Weinan Z" <weinan.z.li@intel.com>,
	"Han, Xu" <xu.han@intel.com>
Subject: Re: About dealing with CSB.context element switch in execlist mode.
Date: Wed, 25 Nov 2015 13:14:42 +0000	[thread overview]
Message-ID: <5655B442.4020602@intel.com> (raw)
In-Reply-To: <F3B0350DF4CB6849A642218320DE483D4A518C81@SHSMSX101.ccr.corp.intel.com>

On 11/25/2015 1:00 PM, Wang, Zhi A wrote:
> Another question about EXECLIST is: Can a preemption happen between element switch?
>
> I know this is beyond the scope of i915 a little. I'm just curious if it's possible.
>
> Let's say we have context A B C
>
> At first, we submit context A B in one ELSP write.
> Then, we submit context C in another ELSP write at some time.
>
> If context A or B is running and gets preempted, then there will be CSB.preempted in CSB buffer. This is the normal behavior.
>
> I'm wondering that if there is any possibility that a preemption can happen between the two elements.
>
> Then the CSB should look like:
>
> [CSB 0 idle-to-active]
> [CSB 1 CTX A element_switch/context_complete]
> [CSB 2 CTX C active-to-idle/context_complete]
>
> Is it possible?

I would expect to always have a preempted event in the CSB, even in the 
remote case that A already completed and B hasn't started; there was an 
active execlist and it has been replaced by a new one:

  [CSB 0 idle-to-active]
  [CSB 1 CTX A element_switch/context_complete]
  [CSB 2 preempted ]
  [CSB 3 CTX C active-to-idle/context_complete]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-11-25 13:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24 13:33 About dealing with CSB.context element switch in execlist mode Wang, Zhi A
2015-11-25 12:47 ` Michel Thierry
2015-11-25 12:51   ` Wang, Zhi A
2015-11-25 13:00   ` Wang, Zhi A
2015-11-25 13:14     ` Michel Thierry [this message]
2015-11-25 13:17       ` Wang, Zhi A
2015-11-26 16:47         ` Dave Gordon

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=5655B442.4020602@intel.com \
    --to=michel.thierry@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=min.he@intel.com \
    --cc=weinan.z.li@intel.com \
    --cc=xu.han@intel.com \
    --cc=zhi.a.wang@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.