From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Hellstrom Subject: Re: [PATCH v2] drm: enable render-nodes by default Date: Thu, 20 Mar 2014 15:59:17 +0100 Message-ID: <532B0245.7050504@vmware.com> References: <1394977400-10465-1-git-send-email-dh.herrmann@gmail.com> <1395074636-32337-1-git-send-email-dh.herrmann@gmail.com> <532A8E07.5000208@shipmail.org> <532AAB78.6010500@vmware.com> <532AB481.40309@vmware.com> <532AC2C2.5030606@vmware.com> <20140320143600.GA2020@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Received: from smtp-outbound-1.vmware.com (smtp-outbound-1.vmware.com [208.91.2.12]) by gabe.freedesktop.org (Postfix) with ESMTP id D96066E0CD for ; Thu, 20 Mar 2014 07:59:20 -0700 (PDT) In-Reply-To: <20140320143600.GA2020@gmail.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Jerome Glisse Cc: Daniel Vetter , "dri-devel@lists.freedesktop.org" List-Id: dri-devel@lists.freedesktop.org On 03/20/2014 03:36 PM, Jerome Glisse wrote: > > In any case this is not a render node issue and there is no reasons to fo= rce > full VRAM eviction or anything like that. This comment suggests you haven't read the discussion fully. VRAM eviction was discussed in the context of legacy nodes. This is a render node issue because with legacy nodes you can work around insufficient command checking. With render nodes you can't. /Thomas > Cheers, > J=E9r=F4me