WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] vTPM - Xenbus interaction

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] vTPM - Xenbus interaction
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
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1275925048; bh=Efy/wubyhSl4cCxBC3QNPY/SG6PdM8PfyjALU7icBAk=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=5wLN2CnCvFuzsMDn22iVdWMMbXKMdIuyBT9MPxDKnUMmgmqGgRfZKeIQ4fehPwukWRXoOnsd8AcToNEYi6s3GwKFCh7P8YOfc2FYwN03c29OSrpooRdIwjVLu1UzzkdwzEqE2ItoMsg2snctAUZYulGUa/kWKdhfsCeklDyubgs=
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=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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
<Prev in Thread] Current Thread [Next in Thread>