[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20090624150506.GK1784@ucw.cz>
Date: Wed, 24 Jun 2009 17:05:06 +0200
From: Pavel Machek <pavel@....cz>
To: Joseph Cihula <joseph.cihula@...el.com>
Cc: linux-kernel@...r.kernel.org, mingo@...e.hu, arjan@...ux.intel.com,
hpa@...or.com, andi@...stfloor.org, chrisw@...s-sol.org,
jmorris@...ei.org, jbeulich@...ell.com, peterm@...hat.com,
gang.wei@...el.com, shane.wang@...el.com
Subject: Re: [RFC v5][PATCH 3/4] intel_txt: Intel(R) TXT Sx shutdown support
On Mon 2009-06-22 17:41:38, 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) 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.
I don't get this. In case of hibernation... how do you 'protect' the
data in memory?
This really needs big Documentation/ patch explaining the design
before it can be reviewed properly.
What does it protect? All kernel memory? How does it handle S3? Who
does encryption for hibernation?
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists