From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:56196)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1Xz64Y-0000BG-VB
	for qemu-devel@nongnu.org; Thu, 11 Dec 2014 10:54:41 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1Xz64S-0006qt-OI
	for qemu-devel@nongnu.org; Thu, 11 Dec 2014 10:54:34 -0500
Received: from mx1.redhat.com ([209.132.183.28]:58673)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1Xz64S-0006qK-Ho
	for qemu-devel@nongnu.org; Thu, 11 Dec 2014 10:54:28 -0500
Received: from int-mx10.intmail.prod.int.phx2.redhat.com
	(int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23])
	by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id sBBFsRJY023117
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256
	verify=FAIL)
	for <qemu-devel@nongnu.org>; Thu, 11 Dec 2014 10:54:27 -0500
Message-ID: <1418313265.1664.63.camel@nilsson.home.kraxel.org>
From: Gerd Hoffmann <kraxel@redhat.com>
Date: Thu, 11 Dec 2014 16:54:25 +0100
In-Reply-To: <20141211154628.GP23831@redhat.com>
References: <1418295956-22479-1-git-send-email-kraxel@redhat.com>
	<20141211123230.GF23831@redhat.com>
	<1418311740.1664.48.camel@nilsson.home.kraxel.org>
	<20141211154628.GP23831@redhat.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [RfC PATCH 0/3] sdl2: add opengl rendering support
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org

  Hi,

> Consider mutli-head for a minute. There could be a scenario where we
> want to allow 3d usage in one head, but not in the other head. This
> might in turn mean we would want to enable opengl in one display
> backend but not the other, depending on which head was connected.
> eg so only one tenant gets exclusive usage of the 3d features.
> A single -global wouldn't allow that to be done.

Would be more multi-seat, but yes, obscure but valid use case.

See reply to paolo, when splitting UI initialization into two stages
this should be doable with a per-UI option.

cheers,
  Gerd