From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wilson Subject: [RFC] Preserve stolen objects across initialisation Date: Sat, 21 Apr 2012 17:35:44 +0100 Message-ID: <1335026161-15054-1-git-send-email-chris@chris-wilson.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from fireflyinternet.com (smtp.fireflyinternet.com [109.228.6.236]) by gabe.freedesktop.org (Postfix) with ESMTP id DE0EA9E864 for ; Sat, 21 Apr 2012 09:36:40 -0700 (PDT) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org The goal of this series is to introduce a GEM object that is backend by stolen memory and able to wrap preallocated objects before we have fully initialised GEM. And then to keep those objects around as we do intialise GEM for continued use afterwards. This patchset is slightly larger than strictly required, as I thinking of how to introduce stolen objects, I realised that it would be much easier if I could base it on the list removal and disassociation between obj->pages and obj->gtt_space. -Chris