From: Pavel Machek <pavel@suse.cz>
To: "Cihula, Joseph" <joseph.cihula@intel.com>
Cc: linux-kernel@vger.kernel.org, "Wang,
Shane" <shane.wang@intel.com>, "Wei, Gang" <gang.wei@intel.com>,
"Van De Ven, Arjan" <arjan.van.de.ven@intel.com>,
"Mallick, Asit K" <asit.k.mallick@intel.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
Chris Wright <chrisw@redhat.com>,
Jan Beulich <jbeulich@novell.com>,
mingo@elte.hu, tytso@mit.edu
Subject: Re: [RFC][PATCH 3/3] TXT: Intel(R) TXT and tboot kernel support
Date: Thu, 9 Oct 2008 15:05:18 +0200 [thread overview]
Message-ID: <20081009130518.GE1623@ucw.cz> (raw)
In-Reply-To: <D936D925018D154694D8A362EEB0892005AC10E3@orsmsx416.amr.corp.intel.com>
Hi!
> (large) Patch inline below (and still attached for those who prefer it).
>
> Linux kernel changes to support tboot and Intel TXT.
Please pick a better acronym. TXT is already taken.
> +struct tboot_acpi_sleep_info {
> + u16 pm1a_cnt;
> + u16 pm1b_cnt;
> + u16 pm1a_evt;
> + u16 pm1b_evt;
> + u16 pm1a_cnt_val;
> + u16 pm1b_cnt_val;
> +} __attribute__ ((__packed__));
> +
> +struct tboot_shared {
> + /* version 0x01+ fields: */
> + struct tboot_uuid uuid; /* TBOOT_SHARED_UUID */
> + u32 version; /* Version number: 2 is current */
> + u32 log_addr; /* physical addr of tb_log_t log */
> + u32 shutdown_entry32; /* entry point for tboot shutdown from
> 32b */
> + u32 shutdown_entry64; /* entry point for tboot shutdown from
> 64b */
should these be function pointers?
> + u32 shutdown_type; /* type of shutdown (TB_SHUTDOWN_*) */
> + u32 s3_tb_wakeup_entry;/* entry point for tboot s3 wake up */
> + u32 s3_k_wakeup_entry; /* entry point for kernel s3 wake up */
> + struct tboot_acpi_sleep_info
> + acpi_sinfo; /* where kernel put acpi sleep info in
> Sx */
> + u8 reserved[52]; /* this pad is for compat with old field
> */
> + /* version 0x02+ fields: */
> + u32 tboot_base; /* starting addr for tboot */
> + u32 tboot_size; /* size of tboot */
> +} __attribute__ ((__packed__));
> +
> +/* {663C8DFF-E8B3-4b82-AABF-19EA4D057A08} */
> +#define TBOOT_SHARED_UUID \
> + ((struct tboot_uuid){ 0x663c8dff, 0xe8b3, 0x4b82,
> 0xaabf, \
> + { 0x19, 0xea, 0x4d, 0x5, 0x7a, 0x8 } })
Can we use normal magic number like rest of kernel does?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-10-09 13:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 20:34 [RFC][PATCH 3/3] TXT: Intel(R) TXT and tboot kernel support Cihula, Joseph
2008-10-07 21:05 ` James Morris
2008-10-07 21:09 ` Cihula, Joseph
2008-10-07 21:44 ` James Morris
2008-10-09 13:05 ` Pavel Machek [this message]
2008-10-09 17:50 ` Chris Wright
2008-10-09 20:35 ` Cihula, Joseph
2008-10-09 21:34 ` Chris Wright
2008-10-09 17:25 ` Jeremy Fitzhardinge
2008-10-09 18:28 ` Chris Wright
2008-10-09 18:39 ` Cihula, Joseph
2008-10-08 0:52 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2008-10-07 23:29 Joseph Cihula
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=20081009130518.GE1623@ucw.cz \
--to=pavel@suse.cz \
--cc=arjan.van.de.ven@intel.com \
--cc=asit.k.mallick@intel.com \
--cc=chrisw@redhat.com \
--cc=gang.wei@intel.com \
--cc=jbeulich@novell.com \
--cc=joseph.cihula@intel.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=shane.wang@intel.com \
--cc=tytso@mit.edu \
/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.