From: Peter Jones <pjones@redhat.com>
To: "Cihula, Joseph" <joseph.cihula@intel.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@elte.hu" <mingo@elte.hu>,
"arjan@linux.intel.com" <arjan@linux.intel.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"andi@firstfloor.org" <andi@firstfloor.org>,
"chrisw@sous-sol.org" <chrisw@sous-sol.org>,
"jmorris@namei.org" <jmorris@namei.org>,
"jbeulich@novell.com" <jbeulich@novell.com>,
"peterm@redhat.com" <peterm@redhat.com>,
"Wei, Gang" <gang.wei@intel.com>,
"Wang, Shane" <shane.wang@intel.com>
Subject: Re: [RFC v5][PATCH 0b/4] intel_txt: Intel(R) Trusted Execution Technology support for Linux - Details
Date: Wed, 24 Jun 2009 16:29:16 -0400 [thread overview]
Message-ID: <4A428C9C.6080702@redhat.com> (raw)
In-Reply-To: <4F65016F6CB04E49BFFA15D4F7B798D9A2A3C1AE@orsmsx506.amr.corp.intel.com>
On 06/23/2009 05:04 PM, Cihula, Joseph wrote:
>> From: Alan Cox [mailto:alan@lxorguk.ukuu.org.uk] Sent: Tuesday,
>> June 23, 2009 2:11 AM
>>
>> Is there a summary of what has changes from RFC v4 ?
>
> - The monolithic patch was broken into four patches that represent
> discrete functionality (boot and build, reboot/halt shutdown, Sx
> shutdown, forcing DMAR on). An appropriate (and more descriptive)
> patch description was added to each patch.
>
> - Small stylistic cleanups (capitalization, comment wording,
> whitespace, etc.).
>
> - The code in hwsleep.c that populated the tboot ACPI structures was
> moved into its own function in tboot.c.
>
> - Use pr_warning(), pr_info(), pr_debug().
>
> - Moved some #include's from the middle of tboot.c to the top.
>
> - Changed the memory type of the tboot shared page from
> E820_UNUSABLE to E820_RESERVED (really a change to tboot, but
> requires a change here in the checking code).
>
> And the new patches that I'm about to send have notes in the top
> indicating their changes from the previous versions.
So it still requires a giant binary blob to be loaded into main
memory to be executed by the main CPU with full privileges (or
plausibly even more lattitude than kernel normally has), right?
--
Peter
next prev parent reply other threads:[~2009-06-24 20:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 0:41 [RFC v5][PATCH 0b/4] intel_txt: Intel(R) Trusted Execution Technology support for Linux - Details Joseph Cihula
2009-06-23 9:11 ` Alan Cox
2009-06-23 21:04 ` Cihula, Joseph
2009-06-24 20:29 ` Peter Jones [this message]
2009-06-24 20:14 ` Dave Jones
2009-06-24 20:37 ` Arjan van de Ven
2009-06-24 20:50 ` Dave Jones
2009-06-24 20:59 ` Matthew Garrett
2009-06-24 22:50 ` Alan Cox
2009-06-25 19:25 ` Cihula, Joseph
2009-06-24 14:41 ` 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=4A428C9C.6080702@redhat.com \
--to=pjones@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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 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.