From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44332) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bDScC-0002Vx-Kn for qemu-devel@nongnu.org; Thu, 16 Jun 2016 04:25:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bDSc8-000636-CR for qemu-devel@nongnu.org; Thu, 16 Jun 2016 04:25:27 -0400 Received: from mx1.redhat.com ([209.132.183.28]:36857) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bDSc8-00062m-7O for qemu-devel@nongnu.org; Thu, 16 Jun 2016 04:25:24 -0400 Date: Thu, 16 Jun 2016 09:25:17 +0100 From: "Daniel P. Berrange" Message-ID: <20160616082517.GC11426@redhat.com> Reply-To: "Daniel P. Berrange" References: <20160120154657.GF13215@redhat.com> <569FADC7.7060301@linux.vnet.ibm.com> <20160120162220.GH13215@redhat.com> <20160121113632.GC2446@work-vm> <57FA3A002D66E049AA7792D931B894C7060F5494@MOKSCY3MSGUSRGB.ITServices.sbc.com> <945CA011AD5F084CBEA3E851C0AB28894B8C3A14@SHSMSX101.ccr.corp.intel.com> <575E92DB.3080904@linux.vnet.ibm.com> <20160615193019.GB7300@work-vm> <5761C092.5070702@linux.vnet.ibm.com> <20160616080520.GA2249@work-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20160616080520.GA2249@work-vm> Subject: Re: [Qemu-devel] [PATCH v5 1/4] Provide support for the CUSE TPM List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Dr. David Alan Gilbert" Cc: Stefan Berger , Stefan Berger , "mst@redhat.com" , "qemu-devel@nongnu.org" , "hagen.lauer@huawei.com" , "Xu, Quan" , "silviu.vlasceanu@gmail.com" , "SERBAN, CRISTINA" , "SHIH, CHING C" On Thu, Jun 16, 2016 at 09:05:20AM +0100, Dr. David Alan Gilbert wrote: > * Stefan Berger (stefanb@linux.vnet.ibm.com) wrote: > > On 06/15/2016 03:30 PM, Dr. David Alan Gilbert wrote: > > > > > > So what was the multi-instance vTPM proxy driver patch set about? > > > > That's for containers. > > Why have the two mechanisms? Can you explain how the multi-instance > proxy works; my brief reading when I saw your patch series seemed > to suggest it could be used instead of CUSE for the non-container case. One of the key things that was/is not appealing about this CUSE approach is that it basically invents a new ioctl() mechanism for talking to a TPM chardev. With in-kernel vTPM support, QEMU probably doesn't need to have any changes at all - its existing driver for talking to TPM char devices ought to just work. All that would be required is libvirt support too configure the vTPM instances. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|