public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 5/5] drm/i915: debugfs entries for [e]LLC
Date: Thu, 4 Jul 2013 11:46:05 -0700	[thread overview]
Message-ID: <20130704184605.GL5488@bwidawsk.net> (raw)
In-Reply-To: <CAKMK7uHKtA5w3UbBY_tHfxqgECxrhgBSYgGGWx7Y8D_SphH8SQ@mail.gmail.com>

On Thu, Jul 04, 2013 at 08:43:58PM +0200, Daniel Vetter wrote:
> On Thu, Jul 4, 2013 at 8:40 PM, Ben Widawsky <ben@bwidawsk.net> wrote:
> > On Thu, Jul 04, 2013 at 08:14:41PM +0200, Daniel Vetter wrote:
> >> On Thu, Jul 04, 2013 at 11:02:07AM -0700, Ben Widawsky wrote:
> >> > To make users life a little easier figuring out what they have on their
> >> > system.
> >> >
> >> > Ideally, I'd really like to report LLC size, but it turned out to be a
> >> > bit of a pain. Maybe I'll revisit it in the future.
> >> >
> >> > Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
> >>
> >> I think a getparam for eLLC would be neat, so that usespace can use it to
> >> tune working set sizes.
> >> -Daniel
> >>
> > And I assume drop debugfs?
> 
> Yeah, I guess the DRM_INFO message in dmesg should be good enough
> then. For userspace's convenience we could even look into exposing the
> LLC size with a getparam.
> -Daniel
>

I would like to do this since we have easy access to cpuid. I know Chad
really wants it. If you'll accept the patch, I'll write it.

> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch

-- 
Ben Widawsky, Intel Open Source Technology Center

  reply	other threads:[~2013-07-04 18:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-04 18:02 [PATCH 1/5] drm/i915/hsw: Set correct Haswell PTE encodings Ben Widawsky
2013-07-04 18:02 ` [PATCH 2/5] drm/i915: Define some of the eLLC magic Ben Widawsky
2013-07-13  0:02   ` Rodrigo Vivi
2013-07-14 20:36     ` Ben Widawsky
2013-07-04 18:02 ` [PATCH 3/5] drm/i915: store eLLC size Ben Widawsky
2013-07-04 18:42   ` [PATCH 3.5/5] drm/i915: Do eLLC detection earlier Ben Widawsky
2013-07-13  0:04     ` Rodrigo Vivi
2013-07-13  9:39     ` Daniel Vetter
2013-07-14 20:37       ` Ben Widawsky
2013-07-16  6:02   ` [PATCH 3/5] drm/i915: store eLLC size Daniel Vetter
2013-07-04 18:02 ` [PATCH 4/5] drm/i915: Use eLLC/LLC by default when available Ben Widawsky
2013-07-04 18:17   ` Daniel Vetter
2013-07-04 18:40     ` Ben Widawsky
2013-07-13  0:08       ` Rodrigo Vivi
2013-07-04 18:02 ` [PATCH 5/5] drm/i915: debugfs entries for [e]LLC Ben Widawsky
2013-07-04 18:14   ` Daniel Vetter
2013-07-04 18:40     ` Ben Widawsky
2013-07-04 18:43       ` Daniel Vetter
2013-07-04 18:46         ` Ben Widawsky [this message]
2013-07-09 18:35           ` Chad Versace
2013-07-09 20:16             ` Ben Widawsky
2013-07-04 18:47   ` [PATCH 6/6] drm/i915: Add a param for eLLC size Ben Widawsky
2013-07-16  6:10     ` Daniel Vetter
2013-07-13  0:11   ` [PATCH 5/5] drm/i915: debugfs entries for [e]LLC Rodrigo Vivi
2013-07-13  0:00 ` [PATCH 1/5] drm/i915/hsw: Set correct Haswell PTE encodings Rodrigo Vivi
2013-07-14 20:34   ` Ben Widawsky
2013-07-15 14:16 ` Damien Lespiau
2013-07-15 14:23 ` Damien Lespiau
2013-07-15 16:54   ` Ben Widawsky
2013-07-16  6:00     ` Daniel Vetter

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=20130704184605.GL5488@bwidawsk.net \
    --to=ben@bwidawsk.net \
    --cc=daniel@ffwll.ch \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox