From: Kenneth Graunke <kenneth@whitecape.org>
To: "Yang, Rong R" <rong.r.yang@intel.com>,
"Zou, Nanhai" <nanhai.zou@intel.com>
Cc: mesa-dev <mesa-dev@lists.freedesktop.org>,
Ben Widawsky <ben@bwidawsk.net>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [Mesa-dev] How user space applications load registers on HSW?
Date: Mon, 12 May 2014 11:04:02 -0700 [thread overview]
Message-ID: <53710D12.50704@whitecape.org> (raw)
In-Reply-To: <7597C9376C272A4AB2D29E91550B7B0901354A7C@shsmsx102.ccr.corp.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 754 bytes --]
On 05/12/2014 01:02 AM, Yang, Rong R wrote:
> Hi, Ken,
>
> Thanks for your patch. But how do you release your driver on the HSW
> products? If can't LRI/LRM from userspace batches, almost all of
> OpenCL application can't run. So if I want to announce that the
> OpenCL driver support HSW, it must have a way to load L3CTRLREG2 and
> L3CTRLREG3.
Most of the OpenGL features don't need LRI/LRM. Currently, only a few
OpenGL 4.0 extensions (ARB_transform_feedback2/3/instanced) and the
perforrmance monitoring extensions need LRI/LRM...and we just don't ship
those on Haswell yet. I'd really like to, but we can't yet.
You'll need to talk to Jesse, Brad, and Daniel to figure out when the
kernel interface will be finished.
--Ken
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-05-12 18:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140506181145.GA25374@bwidawsk.net>
2014-05-06 18:57 ` [rong.r.yang@intel.com: [Intel-gfx] How user space applications load registers on HSW?] Kenneth Graunke
2014-05-12 8:02 ` [Mesa-dev] [rong.r.yang@intel.com: " Yang, Rong R
2014-05-12 18:04 ` Kenneth Graunke [this message]
2014-05-13 6:11 ` [rong.r.yang@intel.com: [Intel-gfx] " Daniel Vetter
2014-05-13 7:47 ` Zou, Nanhai
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=53710D12.50704@whitecape.org \
--to=kenneth@whitecape.org \
--cc=ben@bwidawsk.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mesa-dev@lists.freedesktop.org \
--cc=nanhai.zou@intel.com \
--cc=rong.r.yang@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