On Mon, 2017-01-09 at 08:49 -0700, Jason Gunthorpe wrote: > On Sun, Jan 08, 2017 at 04:58:33PM -0800, James Bottomley wrote: > > I noticed, while playing around with the kernel based resource > > manager, that it's very advantageous to have an emulated TPM device > > to > > test now that I'm playing with startup sequences and TPM ownership. > > > > This is an emulator pass through. It connects an existing emulator > > running on the platform (expected to be the MS Simulator available > > from https://sourceforge.net/projects/ibmswtpm2/) and adds it as an > > in-kernel device, meaning you can exercise the kernel TPM interface > > from either inside the kernel or using the device node. > > > > The tpm-emulator simply connects to the command socket of the MS > > simulator (on localhost:2321) and proxies TPM commands. The > > destination and port are settable as module parameters meaning that > > the TPM emulator doesn't have to be running locally. > > What is wrong with using drivers/char/tpm/tpm_vtpm_proxy.c and doing > the socket connection in userspace?
Simplicity, mostly. It's a tiny driver to proxy the network protocol directly, meaning it's much easier to set up. Plus if you're running smoke tests in a VM you can actually run the emulator in the host without any additional code in the guest. James ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ tpmdd-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tpmdd-devel
