From: Daniel Vetter <daniel@ffwll.ch>
To: jeff.mcgee@intel.com
Cc: intel-gfx@lists.freedesktop.org, beignet@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Export total subslice and EU counts
Date: Tue, 3 Mar 2015 09:56:49 +0100 [thread overview]
Message-ID: <20150303085649.GK18775@phenom.ffwll.local> (raw)
In-Reply-To: <20150303085439.GJ18775@phenom.ffwll.local>
On Tue, Mar 03, 2015 at 09:54:39AM +0100, Daniel Vetter wrote:
> On Mon, Mar 02, 2015 at 03:37:32PM -0800, jeff.mcgee@intel.com wrote:
> > From: Jeff McGee <jeff.mcgee@intel.com>
> >
> > Setup new I915_GETPARAM ioctl entries for subslice total and
> > EU total. Userspace drivers need these values when constructing
> > GPGPU commands. This kernel query method is intended to replace
> > the PCI ID-based tables that userspace drivers currently maintain.
> > The kernel driver can employ fuse register reads as needed to
> > ensure the most accurate determination of GT config attributes.
> > This first became important with Cherryview in which the config
> > could differ between devices with the same PCI ID.
> >
> > The kernel detection of these values is device-specific and not
> > included in this patch. Because zero is not a valid value for any of
> > these parameters, a value of zero is interpreted as unknown for the
> > device. Userspace drivers should continue to maintain ID-based tables
> > for older devices not supported by the new query method.
> >
> > For: VIZ-4636
> > Signed-off-by: Jeff McGee <jeff.mcgee@intel.com>
> > ---
> > drivers/gpu/drm/i915/i915_dma.c | 10 ++++++++++
> > include/uapi/drm/i915_drm.h | 2 ++
> > 2 files changed, 12 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_dma.c b/drivers/gpu/drm/i915/i915_dma.c
> > index 053e178..9350ea2 100644
> > --- a/drivers/gpu/drm/i915/i915_dma.c
> > +++ b/drivers/gpu/drm/i915/i915_dma.c
> > @@ -150,6 +150,16 @@ static int i915_getparam(struct drm_device *dev, void *data,
> > case I915_PARAM_MMAP_VERSION:
> > value = 1;
> > break;
> > + case I915_PARAM_SUBSLICE_TOTAL:
> > + value = INTEL_INFO(dev)->subslice_total;
> > + if (!value)
> > + return -ENODEV;
> > + break;
> > + case I915_PARAM_EU_TOTAL:
> > + value = INTEL_INFO(dev)->eu_total;
> > + if (!value)
> > + return -ENODEV;
>
> I need the corresponding userspace support before I can merged this.
Strike that, I've missed the beignet support. As soon as beignet
maintainers have that reviewed I can pull this in.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-03-03 8:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 23:37 [PATCH] drm/i915: Export total subslice and EU counts jeff.mcgee
2015-03-03 1:26 ` Jeff McGee
2015-03-03 8:54 ` Daniel Vetter
2015-03-03 8:56 ` Daniel Vetter [this message]
2015-03-05 4:35 ` Zhigang Gong
2015-03-06 18:44 ` [Beignet] " Jeff McGee
2015-03-09 0:10 ` Zhigang Gong
2015-03-13 17:03 ` [Beignet] " Daniel Vetter
2015-03-06 19:23 ` Jeff McGee
2015-03-09 23:06 ` [PATCH v2] " jeff.mcgee
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=20150303085649.GK18775@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=beignet@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jeff.mcgee@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