From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753314AbbIJOwu (ORCPT ); Thu, 10 Sep 2015 10:52:50 -0400 Received: from mx1.redhat.com ([209.132.183.28]:39389 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752894AbbIJOws (ORCPT ); Thu, 10 Sep 2015 10:52:48 -0400 Message-ID: <1441896765.11233.25.camel@redhat.com> Subject: Re: [PATCH 5/5] virtgpu: mark as a render gpu From: Gerd Hoffmann To: Emil Velikov Cc: ML dri-devel , Dave Airlie , open list , "open list:VIRTIO GPU DRIVER" Date: Thu, 10 Sep 2015 16:52:45 +0200 In-Reply-To: References: <1441798946-26233-1-git-send-email-kraxel@redhat.com> <1441798946-26233-6-git-send-email-kraxel@redhat.com> <1441895002.11233.6.camel@redhat.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, > > Dave? Looking at the ioctls they are all fine for render nodes, there > > isn't anything modesetting related in the device-specific ioctls. > > > > Correct? > > > Unless I've overdone the coffee this time - modesetting is done via > the card# node, while render via either card# or renderD#. Exactly, thats why anything modesetting-related must be disabled for renderD#. Looking at the virtio-gpu device-specific ioctls I don't think there is anything doing modesetting (which we would have to leave out), so we can apply DRM_RENDER_ALLOW everythere I think. Or maybe there is a global switch to flip DRM_RENDER_ALLOW for the whole list ... cheers, Gerd