mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: James Morris <jmorris@namei.org>,
	Joseph Cihula <joseph.cihula@intel.com>,
	Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, arjan@linux.intel.com,
	hpa@zytor.com, andi@firstfloor.org,
	Chris Wright <chrisw@sous-sol.org>,
	jbeulich@novell.com, peterm@redhat.com, gang.wei@intel.com,
	shane.wang@intel.com
Subject: Re: [RFC v4][PATCH 2/2] intel_txt: Intel(R) TXT and tboot kernel support
Date: Fri, 19 Jun 2009 11:34:14 -0700	[thread overview]
Message-ID: <20090619183414.GG19771@sequoia.sous-sol.org> (raw)
In-Reply-To: <20090619150514.GE1389@ucw.cz>

* Pavel Machek (pavel@ucw.cz) wrote:
> What are non-evil uses of this code?

The most common use case I've heard requested from real live
customers[1] is...you guessed it...trusted boot.

This is typically in the context of virtualization and data centers or
clouds.  The concerns being addressed are:

* confidence that the hardware is running the VMM that the hardware
  owner configured it w/, since they are on the hook for providing a
  safe service for each VM running on that hardware

* flip side of that is an additional layer protecting against malicious
  VM that is using some VMM hole to try and subvert the host w/ a VMM
  of their own

thanks,
-chris
--

[1] as opposed to hardware vendors pushing a feature

  parent reply	other threads:[~2009-06-19 18:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05 21:38 Joseph Cihula
2009-06-12  5:12 ` James Morris
2009-06-12 10:23   ` Andi Kleen
2009-06-19 15:05   ` Pavel Machek
2009-06-19 17:52     ` Valdis.Kletnieks
2009-06-19 19:11       ` Alan Cox
2009-06-19 20:27         ` Alan Cox
2009-06-22  1:33           ` James Morris
2009-06-19 21:22       ` Pavel Machek
2009-06-19 18:34     ` Chris Wright [this message]
2009-06-22  1:54       ` James Morris
2009-06-26 21:30         ` Pavel Machek
2009-06-28 22:46           ` James Morris
2009-08-24  9:43             ` Pavel Machek

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=20090619183414.GG19771@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=andi@firstfloor.org \
    --cc=arjan@linux.intel.com \
    --cc=gang.wei@intel.com \
    --cc=hpa@zytor.com \
    --cc=jbeulich@novell.com \
    --cc=jmorris@namei.org \
    --cc=joseph.cihula@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pavel@ucw.cz \
    --cc=peterm@redhat.com \
    --cc=shane.wang@intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome