From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: joseph.cihula@intel.com
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
arjan@linux.intel.com, hpa@zytor.com, andi@firstfloor.org,
chrisw@sous-sol.org, jmorris@namei.org, jbeulich@novell.com,
peterm@redhat.com, gang.wei@intel.com, shane.wang@intel.com
Subject: Re: [RFC v6][PATCH 3/4] intel_txt: Intel(R) TXT Sx shutdown support
Date: Fri, 3 Jul 2009 01:15:23 +0200 [thread overview]
Message-ID: <200907030115.24552.rjw@sisk.pl> (raw)
In-Reply-To: <4A4ACA6B.4050705@intel.com>
On Wednesday 01 July 2009, Joseph Cihula wrote:
> Support for graceful handling of sleep states (S3/S4/S5) after an Intel(R) TXT launch.
>
> Without this patch, attempting to place the system in one of the ACPI sleep
> states (S3/S4/S5)
To be precise, S5 is not a sleep state.
> will cause the TXT hardware to treat this as an attack and
> will cause a system reset, with memory locked. Not only may the subsequent
> memory scrub take some time, but the platform will be unable to enter the
> requested power state.
>
> This patch calls back into the tboot so that it may properly and securely clean
> up system state and clear the secrets-in-memory flag, after which it will place
> the system into the requested sleep state using ACPI information passed by the kernel.
Is there any documentation describing how ACPI sleeps states are supposed to
work with the TXT hardware?
Rafael
next prev parent reply other threads:[~2009-07-02 23:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 2:31 Joseph Cihula
2009-07-02 21:29 ` Pavel Machek
2009-07-02 23:15 ` Rafael J. Wysocki [this message]
2009-07-03 6:15 ` Andi Kleen
2009-07-04 0:11 ` Rafael J. Wysocki
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=200907030115.24552.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=andi@firstfloor.org \
--cc=arjan@linux.intel.com \
--cc=chrisw@sous-sol.org \
--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=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
all inboxes | Powered by JetHome®