[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.00.0906242045290.18503@tundra.namei.org>
Date: Wed, 24 Jun 2009 20:46:50 +1000 (EST)
From: James Morris <jmorris@...ei.org>
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,
jbeulich@...ell.com, peterm@...hat.com, gang.wei@...el.com,
shane.wang@...el.com
Subject: Re: [RFC v5][PATCH 2/4] intel_txt: Intel(R) TXT reboot/halt shutdown
support
On Mon, 22 Jun 2009, Joseph Cihula wrote:
> Support for graceful handling of kernel reboots after an Intel(R) TXT launch.
>
> Without this patch, attempting to reboot or halt the system will cause the
> TXT hardware to lock memory upon system restart because the secrets-in-memory
> flag that was set on launch was never cleared. This will in turn cause BIOS
> to execute a TXT Authenticated Code Module (ACM) that will scrub all of memory
> and then unlock it. Depending on the amount of memory in the system and its type,
> this may take some time.
>
Does this mean that after a power failure, the system will perform this
memory scrub on the next boot? How long does it take per MB on a typical
system?
--
James Morris
<jmorris@...ei.org>
--
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