[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5f3869f6-f491-4092-bdc3-40790681f2b1@email.android.com>
Date: Thu, 11 Apr 2013 06:03:50 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Andi Kleen <andi@...stfloor.org>, 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>,
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
Kees posted that one too.
Andi Kleen <andi@...stfloor.org> wrote:
>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
--
Sent from my mobile phone. Please excuse brevity and lack of formatting.
--
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