[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m261ztxp55.fsf@firstfloor.org>
Date: Thu, 11 Apr 2013 04:50:14 -0700
From: Andi Kleen <andi@...stfloor.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: Kees Cook <keescook@...omium.org>, Alexander Duyck <alexander.h.duyck@...el.com>, Alex Shi <alex.shi@...el.com>, Jeremy Fitzhardinge <jeremy@...p.org>, Will Drewry <wad@...omium.org>, Julien Tinnes <jln@...gle.com>, Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>, Frederic Weisbecker <fweisbec@...il.com>, Dan Rosenberg <drosenberg@...curity.com>, x86@...nel.org, linux-kernel@...r.kernel.org, Steven Rostedt <rostedt@...dmis.org>, Borislav Petkov <borislav.petkov@....com>, Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>, kernel-hardening@...ts.openwall.com, Thomas Gleixner <tglx@...utronix.de>, "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>, virtualization@...ts.linux-foundation.org, xen-devel@...ts.xensource.com
Subject: Re: [PATCH v3] x86: use a read-only IDT alias on all CPUs
Ingo Molnar <mingo@...nel.org> writes:
>
> This looks very nice to me now. Peter, any objections?
it seems pointless without randomized main kernel text location, because
the IDT will be still at a known per kernel fixed writable location in
the direct mapping.
As long as such randomization is not there it just wastes a TLB entry.
-Andi
--
ak@...ux.intel.com -- Speaking for myself only
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
