From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: pin OABUFFER to GGTT
Date: Tue, 1 Jul 2014 20:54:27 +0100
Message-ID: <20140701195427.GA11155@nuc-i3427.alporthouse.com>
References: <92648605EABDA246B775AAB04C95A7A3137EB4F3@IRSMSX103.ger.corp.intel.com>
 <20140701163017.GA7371@nuc-i3427.alporthouse.com>
 <92648605EABDA246B775AAB04C95A7A3137EB523@IRSMSX103.ger.corp.intel.com>
 <20140701165149.GB7371@nuc-i3427.alporthouse.com>
 <92648605EABDA246B775AAB04C95A7A3137EB5E3@IRSMSX103.ger.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <intel-gfx-bounces@lists.freedesktop.org>
Received: from fireflyinternet.com (mail.fireflyinternet.com [87.106.93.118])
 by gabe.freedesktop.org (Postfix) with ESMTP id D6DB36E292
 for <Intel-gfx@lists.freedesktop.org>; Tue,  1 Jul 2014 12:54:44 -0700 (PDT)
Content-Disposition: inline
In-Reply-To: <92648605EABDA246B775AAB04C95A7A3137EB5E3@IRSMSX103.ger.corp.intel.com>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/intel-gfx>,
 <mailto:intel-gfx-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/intel-gfx>
List-Post: <mailto:intel-gfx@lists.freedesktop.org>
List-Help: <mailto:intel-gfx-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/intel-gfx>,
 <mailto:intel-gfx-request@lists.freedesktop.org?subject=subscribe>
Errors-To: intel-gfx-bounces@lists.freedesktop.org
Sender: "Intel-gfx" <intel-gfx-bounces@lists.freedesktop.org>
To: "Mateo Lozano, Oscar" <oscar.mateo@intel.com>
Cc: "Intel-gfx@lists.freedesktop.org" <Intel-gfx@lists.freedesktop.org>, "Madajczak, Tomasz" <Tomasz.Madajczak@intel.com>
List-Id: intel-gfx@lists.freedesktop.org

On Tue, Jul 01, 2014 at 05:16:30PM +0000, Mateo Lozano, Oscar wrote:
> > The issue is they need:
> > 
> > A) A buffer object.
> > B) Bound to GGTT.
> > C) That userspace knows the GGTT offset of, so that they can program
> > OABUFFER with it.
> > D) That userspace can map so that they can read the reported counters.
> > 
> > They used to create a bo, call bo_pin on it, use args->offset to program
> > OABUFFER (via MI_LOAD_REGISTER_IMM, I imagine), map it and read the
> > counter values. They cannot do this anymore.
> 
> The answer might be that all of this needs to be done by the kernel itself, but then we need to provide an interface to userspace...

Yes. If you need to pin a buffer for a register, then it needs to be
handled by the kernel. Especially one that provides information about
other users.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre