[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] vTPM - Xenbus interaction


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: ramya jayaram <ramyamasti@xxxxxxxxx>
  • Date: Mon, 7 Jun 2010 21:07:28 +0530 (IST)
  • Delivery-date: Tue, 15 Jun 2010 03:02:32 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=b/JPSdnhWJTKuDmG81v2Q1A3nntdyb7O/YP0CGXiB9kc28LAuylooEDz7gFVBsvbCNbXxH4CINtisLVWTB7dDfa4IeALC9loZfYVOYOiSyGnKn/gtT13lRaiklR1bsUH3tG5sJYmcTy9+0s0HzvgJj+syNE7vuDL2DLYVUl14CI=;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi all,

I was trying to understand the interaction between the front end and back end drivers for the vTPM implementation in Xen 3.1.0

I understand that the front end and the back end communicate via the memory pages shared by the front end driver. However, the event driven notification mechanism is unclear - where is the the port - irq mapping for both ends stored?

Also, is the Xen store merely used for vTPM persistence or does it serve any other purpose in the communication between the front end and back end drivers for the vTPM in Xen?

Thanks in advance,
Ramya




_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.