[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B198C18.7040500@zytor.com>
Date: Fri, 04 Dec 2009 14:24:24 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Pavel Machek <pavel@....cz>
CC: "Cihula, Joseph" <joseph.cihula@...el.com>,
"Wang, Shane" <shane.wang@...el.com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...e.hu>,
"arjan@...ux.intel.com" <arjan@...ux.intel.com>,
"andi@...stfloor.org" <andi@...stfloor.org>,
"chrisw@...s-sol.org" <chrisw@...s-sol.org>,
"jmorris@...ei.org" <jmorris@...ei.org>,
"jbeulich@...ell.com" <jbeulich@...ell.com>,
"peterm@...hat.com" <peterm@...hat.com>
Subject: Re: [PATCH] intel_txt: add s3 userspace memory integrity verification
On 12/04/2009 02:15 PM, Pavel Machek wrote:
>>>
>>> Are you sure x86-64 kernel & modules is always below 4GB? I don't
>>> think so.
The x86-64 kernel is run where it is loaded by the boot loader. For
most boot loaders, that will mean < 4 GB. This is not the case for
modules, and they cannot and should not rely on modules inside
restricted zone.
This effectively becomes a constraint on whatever boot loader is used to
load the kernel for it to be compatible with tboot.
-hpa
--
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