All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: "Intel-gfx@lists.freedesktop.org"
	<Intel-gfx@lists.freedesktop.org>,
	"Madajczak, Tomasz" <Tomasz.Madajczak@intel.com>,
	"Wilson, Chris" <chris.wilson@intel.com>
Subject: Re: pin OABUFFER to GGTT
Date: Thu, 3 Jul 2014 10:10:48 -0700	[thread overview]
Message-ID: <20140703171047.GA976@bwidawsk.net> (raw)
In-Reply-To: <20140703071732.GA2262@strange.amr.corp.intel.com>

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 time. I think backward compatibility is something
> > that you take into consideration as well.
> 
> So, I just sent a patch reverting the change. Daniel will have an
> opinion about this I'm sure, being the original author. Let see what
> happens when he's back from holidays.
> 
> Cheers,
> 
> -- 
> Damien

Just a note for a future ppgtt people - this adds another way to get
multiple VMAs for a single BO. To this point, it had only been flink,
and dmabuf. IIRC there are few unhandled corner cases for this. Also
note that if the BO is still referenced within a batch, we need the flag
to tell us it needs global binding.

FWIW, I remain in favor of the relocation idea unless someone already
expressed why we need multiple processes to have the relocation info.

-- 
Ben Widawsky, Intel Open Source Technology Center

  reply	other threads:[~2014-07-03 17:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01 16:24 pin OABUFFER to GGTT Mateo Lozano, Oscar
2014-07-01 16:30 ` Chris Wilson
2014-07-01 16:34   ` Mateo Lozano, Oscar
2014-07-01 16:51     ` Chris Wilson
2014-07-01 17:13       ` Mateo Lozano, Oscar
2014-07-01 17:16       ` Mateo Lozano, Oscar
2014-07-01 19:54         ` Chris Wilson
2014-07-02  6:40           ` Ben Widawsky
2014-07-02  6:55             ` Chris Wilson
2014-07-02  8:49               ` Mateo Lozano, Oscar
2014-07-02 10:31                 ` Madajczak, Tomasz
2014-07-02 10:49                   ` Damien Lespiau
2014-07-02 11:11                     ` Madajczak, Tomasz
2014-07-02 13:19                       ` Rutkowski, Adam J
2014-07-03  7:17                         ` Damien Lespiau
2014-07-03 17:10                           ` Ben Widawsky [this message]
2014-07-03 20:45                             ` Ben Widawsky
2014-07-02 17:36                   ` Ben Widawsky
2014-07-07 20:43           ` Daniel Vetter
2014-07-07 23:59             ` Bragg, Robert

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=20140703171047.GA976@bwidawsk.net \
    --to=ben@bwidawsk.net \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=Tomasz.Madajczak@intel.com \
    --cc=chris.wilson@intel.com \
    --cc=damien.lespiau@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.