On Mon, Jul 7, 2014 at 9:43 PM, Daniel Vetter wrote:
> On Tue, Jul 01, 2014 at 08:54:27PM +0100, Chris Wilson wrote:
> > On Tue, Jul 01, 2014 at 05:16:30PM +, Mateo Lozano, Oscar wrote:
> > > > The issue is they need:
> > > >
> > > > A) A buffer object.
> > > > B) Bound to GGTT.
> > > > C) Th
On Tue, Jul 01, 2014 at 08:54:27PM +0100, Chris Wilson wrote:
> On Tue, Jul 01, 2014 at 05:16:30PM +, 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
> >
On Thu, Jul 03, 2014 at 10:10:48AM -0700, Ben Widawsky wrote:
> On Thu, Jul 03, 2014 at 08:17:32AM +0100, Damien Lespiau wrote:
> > On Wed, Jul 02, 2014 at 02:19:42PM +0100, Rutkowski, Adam J wrote:
> > > Having said all this, how about restoring the pin_ioctl? At least for
> > > some time? We do h
On Thu, Jul 03, 2014 at 08:17:32AM +0100, Damien Lespiau wrote:
> On Wed, Jul 02, 2014 at 02:19:42PM +0100, Rutkowski, Adam J wrote:
> > Having said all this, how about restoring the pin_ioctl? At least for
> > some time? We do have a use case and moving to other - better -
> > solution would take
On Wed, Jul 02, 2014 at 02:19:42PM +0100, Rutkowski, Adam J wrote:
> Having said all this, how about restoring the pin_ioctl? At least for
> some time? We do have a use case and moving to other - better -
> solution would take time. I think backward compatibility is something
> that you take into c
sage-
> From: Mateo Lozano, Oscar
> Sent: Wednesday, July 02, 2014 10:50 AM
> To: Chris Wilson; Ben Widawsky
> Cc: Intel-gfx@lists.freedesktop.org; Madajczak, Tomasz; Rutkowski, Adam J;
> Jesse Barnes (jbar...@virtuousgeek.org)
> Subject: RE: [Intel-gfx] pin OABUFFER to GGTT
>
>
>
>
you take into
consideration as well.
Thanks
Adam
> -Original Message-
> From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf
> Of Madajczak, Tomasz
> Sent: Wednesday, July 2, 2014 1:12 PM
> To: Lespiau, Damien
> Cc: Ben Widawsky; Intel-gfx@lists.freedesktop.or
, Tomasz
Cc: Mateo Lozano, Oscar; Chris Wilson; Ben Widawsky;
Intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] pin OABUFFER to GGTT
On Wed, Jul 02, 2014 at 10:31:45AM +, Madajczak, Tomasz wrote:
> There isn't any secret or privacy in that OA buffer data - just
> results of
On Wed, Jul 02, 2014 at 10:31:45AM +, Madajczak, Tomasz wrote:
> There isn't any secret or privacy in that OA buffer data - just
> results of performance counters, shown by tools such as GPA/ Vtune.
Chris alludes to the fact that if there's a way for one application to
gather data about other
02, 2014 10:50 AM
To: Chris Wilson; Ben Widawsky
Cc: Intel-gfx@lists.freedesktop.org; Madajczak, Tomasz; Rutkowski, Adam J;
Jesse Barnes (jbar...@virtuousgeek.org)
Subject: RE: [Intel-gfx] pin OABUFFER to GGTT
-
Intel Corpora
> Sent: Wednesday, July 02, 2014 7:56 AM
> To: Ben Widawsky
> Cc: Mateo Lozano, Oscar; Intel-gfx@lists.freedesktop.org; Madajczak,
> Tomasz; Rutkowski, Adam J; Jesse Barnes (jbar...@virtuousgeek.org)
> Subject: Re: [Intel-gfx] pin OABUFFER to GGTT
>
> On Tue, Jul 01, 2014 at 11:
On Tue, Jul 01, 2014 at 11:40:52PM -0700, Ben Widawsky wrote:
> On Tue, Jul 01, 2014 at 08:54:27PM +0100, Chris Wilson wrote:
> > On Tue, Jul 01, 2014 at 05:16:30PM +, Mateo Lozano, Oscar wrote:
> > > > The issue is they need:
> > > >
> > > > A) A buffer object.
> > > > B) Bound to GGTT.
> > >
On Tue, Jul 01, 2014 at 08:54:27PM +0100, Chris Wilson wrote:
> On Tue, Jul 01, 2014 at 05:16:30PM +, 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
> >
On Tue, Jul 01, 2014 at 05:16:30PM +, 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
> -Original Message-
> From: Mateo Lozano, Oscar
> Sent: Tuesday, July 01, 2014 6:14 PM
> To: 'Chris Wilson'
> Cc: Intel-gfx@lists.freedesktop.org; Madajczak, Tomasz; Rutkowski, Adam J;
> Jesse Barnes (jbar...@virtuousgeek.org)
> Subject: RE: [
: Mateo Lozano, Oscar
> > > Cc: Intel-gfx@lists.freedesktop.org; Madajczak, Tomasz
> > > Subject: Re: [Intel-gfx] pin OABUFFER to GGTT
> > >
> > > On Tue, Jul 01, 2014 at 04:24:56PM +, Mateo Lozano, Oscar wrote:
> > > > Submitting again (this time co
Madajczak, Tomasz
> > Subject: Re: [Intel-gfx] pin OABUFFER to GGTT
> >
> > On Tue, Jul 01, 2014 at 04:24:56PM +, Mateo Lozano, Oscar wrote:
> > > Submitting again (this time copying the mailing list correctly):
> > >
> > > The bo_pin ioctl has been d
> -Original Message-
> From: Chris Wilson [mailto:ch...@chris-wilson.co.uk]
> Sent: Tuesday, July 01, 2014 5:30 PM
> To: Mateo Lozano, Oscar
> Cc: Intel-gfx@lists.freedesktop.org; Madajczak, Tomasz
> Subject: Re: [Intel-gfx] pin OABUFFER to GGTT
>
> On Tue, Ju
On Tue, Jul 01, 2014 at 04:24:56PM +, Mateo Lozano, Oscar wrote:
> Submitting again (this time copying the mailing list correctly):
>
> The bo_pin ioctl has been discarded in GEN6+ with this patch:
>
> drm/i915: Reject the pin ioctl on gen6+
>
> Especially with ppgtt this kinda s
Submitting again (this time copying the mailing list correctly):
The bo_pin ioctl has been discarded in GEN6+ with this patch:
drm/i915: Reject the pin ioctl on gen6+
Especially with ppgtt this kinda stopped making sense. And if we
indeed need this to hack around an issue, we nee
20 matches
Mail list logo
