All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Shuaijun Zhang <szhang@research.ait.ie>, dgdegra@tycho.nsa.gov
Cc: xen-devel@lists.xen.org
Subject: Re: Question about VTPM Implementation
Date: Wed, 12 Mar 2014 09:51:46 -0400	[thread overview]
Message-ID: <20140312135145.GD3245@phenom.dumpdata.com> (raw)
In-Reply-To: <CAB2FdyZiRhe5H8wgTKv4+O=y=LMFms_p_=OYGXz-5XU0gF=Hmw@mail.gmail.com>

On Wed, Mar 12, 2014 at 12:32:24PM +0000, Shuaijun Zhang wrote:
> Hi There,
> 
> In the document of VTPM (http://xenbits.xen.org/docs/unstable/misc/vtpm.txt
> ): The Linux dom0 kernel should not try accessing the TPM while the
> vTPM Manager
> domain is accessing it.
> 
> Anyone knows the reason why the dom0 should not access the TPM while vTPM
> Mgr is accessing it?

Lets rope in the maintainer. Perhaps the doc should be updated to explain
this.

> 
> Thanks & Regards,
> Jason

> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2014-03-12 13:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12 12:32 Question about VTPM Implementation Shuaijun Zhang
2014-03-12 13:51 ` Konrad Rzeszutek Wilk [this message]
2014-03-12 14:35   ` Ian Campbell
2014-03-12 14:37   ` [PATCH] docs/vtpm: explain dom0 physical TPM access caveats Daniel De Graaf
2014-03-12 15:20     ` Shuaijun Zhang
2014-03-12 16:36     ` Shuaijun Zhang
2014-03-12 18:39       ` Daniel De Graaf
2014-03-12 23:04         ` Shuaijun Zhang
2014-03-12 23:41           ` Daniel De Graaf
2014-03-13 11:10     ` Ian Campbell
2014-03-13 14:53       ` Daniel De Graaf
2014-03-13 15:59         ` Ian Campbell
2014-03-14 11:01           ` Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140312135145.GD3245@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=dgdegra@tycho.nsa.gov \
    --cc=szhang@research.ait.ie \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.