From: Kenneth Graunke <kenneth@whitecape.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Jason Ekstrand <jason.ekstrand@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] i965: Always try to create a logical context
Date: Mon, 20 Nov 2017 10:43:26 -0800 [thread overview]
Message-ID: <6924474.czhiFrq7ZV@kirito> (raw)
In-Reply-To: <20171120092942.3225-1-chris@chris-wilson.co.uk>
[-- Attachment #1.1: Type: text/plain, Size: 890 bytes --]
On Monday, November 20, 2017 1:29:42 AM PST Chris Wilson wrote:
> Always enable use of HW logical contexts to preserve GPU state between
> batches when the kernel supports such constructs, continuing to enforce
> the required support for gen6+.
>
> At runtime, this effectively removes the BRW_NEW_CONTEXT flag (and the
> upload of invariant state) from the start of every batch for any kernel
> supporting contexts. So long as the older atoms are correctly listening
> to the right flag (NEW_CONTEXT rather than NEW_BATCH) this should
> eliminate a few redundant state uploads for the older platforms.
>
> Cc: Jason Ekstrand <jason.ekstrand@intel.com>
> Cc: Kenneth Graunke <kenneth@whitecape.org>
Nice, I saw Ironlake RC6 go by and was wondering if contexts were up
next :)
It makes sense to use them if the kernel supports them.
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-11-20 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 9:29 [PATCH] i965: Always try to create a logical context Chris Wilson
2017-11-20 18:43 ` Kenneth Graunke [this message]
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=6924474.czhiFrq7ZV@kirito \
--to=kenneth@whitecape.org \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jason.ekstrand@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