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 _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
