From: Chris Wright <chrisw@sous-sol.org>
To: "Cihula, Joseph" <joseph.cihula@intel.com>
Cc: Chris Wright <chrisw@sous-sol.org>, Pavel Machek <pavel@suse.cz>,
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 14:34:33 -0700 [thread overview]
Message-ID: <20081009213433.GG6912@sequoia.sous-sol.org> (raw)
In-Reply-To: <D936D925018D154694D8A362EEB0892005B12E14@orsmsx416.amr.corp.intel.com>
* Cihula, Joseph (joseph.cihula@intel.com) wrote:
> > From: Chris Wright [mailto:chrisw@sous-sol.org]
> > I asked earlier, I didn't understand why it needs to be 2 fields, since
> > it's u32 in both cases and can't both be used at once.
>
> We will look at seeing if we can make a single entry point that detects
> if it was called by 64b code, disable IA32e mode, and then jumps to the
> 32b code.
Yeah, that's exactly what I was thinking. I assumed I missed a piece...
> We did it this way initially because it was easier code to
> keep them separate and has been working for some time. We'll also have
> to adjust Xen if/when we do this.
...which is just this ease of implementation, thanks.
thanks,
-chris
next prev parent reply other threads:[~2008-10-09 21:35 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
2008-10-09 17:50 ` Chris Wright
2008-10-09 20:35 ` Cihula, Joseph
2008-10-09 21:34 ` Chris Wright [this message]
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=20081009213433.GG6912@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--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=pavel@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox