From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:35063)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1bmMcK-0005GD-EB
	for qemu-devel@nongnu.org; Tue, 20 Sep 2016 11:05:53 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1bmMcH-0002h5-85
	for qemu-devel@nongnu.org; Tue, 20 Sep 2016 11:05:52 -0400
Received: from mx1.redhat.com ([209.132.183.28]:44498)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1bmMcH-0002gg-2Z
	for qemu-devel@nongnu.org; Tue, 20 Sep 2016 11:05:49 -0400
References: <00d96f24-5df0-d16b-d4e1-838333989dee@nvidia.com>
	<20160919153600.70599974@t450s.home>
	<8e7e7357-cad4-f9ca-4104-97cadd347a13@redhat.com>
	<20160919162521.3569caa2@t450s.home>
	<32b91537-0d83-a312-db19-7341650c3d4a@nvidia.com>
	<20160920144152.GS25490@redhat.com>
	<3426a530-6741-e567-56d7-735bd5c98b54@redhat.com>
	<20160920145808.GT25490@redhat.com>
From: Paolo Bonzini <pbonzini@redhat.com>
Message-ID: <9e80c4e6-a94f-0fb3-7d57-9ac8ffe53738@redhat.com>
Date: Tue, 20 Sep 2016 17:05:43 +0200
MIME-Version: 1.0
In-Reply-To: <20160920145808.GT25490@redhat.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [RFC v2] libvirt vGPU QEMU integration
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: Kirti Wankhede <kwankhede@nvidia.com>, Alex Williamson <alex.williamson@redhat.com>, Andy Currid <ACurrid@nvidia.com>, "Tian, Kevin" <kevin.tian@intel.com>, Neo Jia <cjia@nvidia.com>, "libvir-list@redhat.com" <libvir-list@redhat.com>, qemu-devel <qemu-devel@nongnu.org>, "Song, Jike" <jike.song@intel.com>, Gerd Hoffmann <kraxel@redhat.com>, "bjsdjshi@linux.vnet.ibm.com" <bjsdjshi@linux.vnet.ibm.com>



On 20/09/2016 16:58, Daniel P. Berrange wrote:
> > > As I've said in my earlier reply - libvirt will *NOT* support passing
> > > arbitrary vendor specific parameters as a blob via the XML. Everything
> > > that appears in the XML must be *fully* specified and explicitly
> > > represented in the XML  as a distinct attribute or element.
> > 
> > Are generic key/value attributes (e.g. a <attribute> element) acceptable?
>
> Only if libvirt has a known list of valid attribute key names upfront.
> We don't want to just blindly expose arbitary vendor specific keys exposed
> by the kernel. Libvirt's job is to ensure the XML representation is vendor
> portable

Ok, then I guess vendor-specific mdev parameters are out completely.  Or
could they be added under a separate namespace, like QEMU passthrough?

Paolo