From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Cc: Eugeni Dodonov <eugeni.dodonov@intel.com>
Subject: Re: [PATCH] sna: check for LLC support
Date: Tue, 17 Jan 2012 18:44:58 +0000 [thread overview]
Message-ID: <e39f63$3c14ed@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <1326824197-4553-1-git-send-email-eugeni.dodonov@intel.com>
On Tue, 17 Jan 2012 16:16:37 -0200, Eugeni Dodonov <eugeni.dodonov@intel.com> wrote:
> Instead of checking for CPU generation, use the libdrm-provided
> I915_PARAM_HAS_LLC instead.
>
> v2: use a define check to verify if we have I915_PARAM_HAS_LLC.
>
> Signed-off-by: Eugeni Dodonov <eugeni.dodonov@intel.com>
I attacked it slightly so that gem_param reported the lack of support so
that we could fallback to guessing by gen for GET_PARAM failure.
Thanks,
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
prev parent reply other threads:[~2012-01-17 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 18:05 [PATCH 1/2] sna: check for LLC support Eugeni Dodonov
2012-01-17 18:05 ` [PATCH 2/2] configure: check for libdrm >= 2.4.31 Eugeni Dodonov
2012-01-17 18:16 ` [PATCH] sna: check for LLC support Eugeni Dodonov
2012-01-17 18:37 ` Daniel Vetter
2012-01-17 18:44 ` Chris Wilson [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='e39f63$3c14ed@fmsmga002.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=eugeni.dodonov@intel.com \
--cc=intel-gfx@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 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.