From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Jackson Subject: Re: [RFC PATCH 00/11] i915 HW context support Date: Tue, 14 Feb 2012 18:17:57 -0500 Message-ID: <4F3AEBA5.6060504@redhat.com> References: <1329253758-24943-1-git-send-email-ben@bwidawsk.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by gabe.freedesktop.org (Postfix) with ESMTP id 3CD339E810 for ; Tue, 14 Feb 2012 15:18:00 -0800 (PST) In-Reply-To: <1329253758-24943-1-git-send-email-ben@bwidawsk.net> 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: Ben Widawsky Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On 2/14/12 4:09 PM, Ben Widawsky wrote: > The IOCTLs defined here may also be used with ppgtt (real ppgtt) but the > interface may be insufficient for that. The contexts do provide a > A... what? Series looks reasonable to me. The one thing that makes me nervous is 4/11 mentioning the BIOS, which honestly seems like an insane thing to let your BIOS have _any_ say in, but then Intel sure does like to give the BIOS a chance to make the OS less functional. The code in 7/11 effectively limits things to between 4k and 1M; does that actually make sense? I can't imagine wanting to allocate only 4k if it turns out we'd always need at least (say) 32k. I have admittedly not read any of the docs on how this is meant to work, apologies if that'd answer this. - ajax