Re: vtpmmgr bug: fails to start if locality!=0

[Ian Campbell <Ian.Campbell@citrix.com>]

CCing Daniel.

On Fri, 2014-10-31 at 17:37 +0200, Emil Condrea wrote:
> 
> I am wondering if this is known issue that when I set locality!=0 to
> vtpmmgr it does not start. It is a bit strange that every call to
> tpm_tis_status returns 255 and device-id is also FFFF: 
> 1.2 TPM (device-id=0xFFFF vendor-id = FFFF rev-id = FF).
> TPM interface capabilities (0xffffffff):
> 
> I am configuring vtpmmgr using:
> 
> kernel="/usr/local/lib/xen/boot/vtpmmgr-stubdom.gz"
> memory=8
> disk=["file:/var/vtpmmgr-stubdom.img,hda,w"]
> name="vtpmmgr"
> iomem=["fed40,5"]
> extra="tpmlocality=2"
> 
> 
> I also tried using :
> iomem=["fed40,1"]
> extra="tpmlocality=0"//works well
> 
> or
> iomem=["fed42,1"]
> extra="tpmlocality=2"
> It seems that everything that is not mapped at fed40-fed41 is
> FFFFFFFF.
> 
> I have an Atmel TPM chipset. 
> 
> Could it be a chipset problem to not handle well different localities?
> 
> When I use locality=0, the device driver info is correct and
> everything works fine:
> 1.2 TPM (device-id=0x3204 vendor-id = 1114 rev-id = 40)
> TPM interface capabilities (0xfd)
> 
> In linux kernel this information is obtained using locality 0 and
> after that other commands execute using specified locality.
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/drivers/char/tpm/tpm_tis.c#n558
> 
> 
> Thanks,
> 
> Emil
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel