Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755385AbaJ1WHh (ORCPT ); Tue, 28 Oct 2014 18:07:37 -0400 Received: from mail.skyhub.de ([78.46.96.112]:60453 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751684AbaJ1WHg (ORCPT ); Tue, 28 Oct 2014 18:07:36 -0400 Date: Tue, 28 Oct 2014 23:07:31 +0100 From: Borislav Petkov To: Mathias Krause Cc: Matt Fleming , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , "linux-kernel@vger.kernel.org" , x86-ml , Matt Fleming Subject: Re: [PATCHv2 1/3] x86, ptdump: Add section for EFI runtime services Message-ID: <20141028220731.GI10873@pd.tnic> References: <20141008151730.GB16892@pd.tnic> <20141008222619.GG16892@pd.tnic> <20141012125515.GA32045@jig.fritz.box> <20141028185756.GD10873@pd.tnic> <20141028201342.GG10873@pd.tnic> <20141028212642.GH10873@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 28, 2014 at 10:49:36PM +0100, Mathias Krause wrote: > Sync only data or kernel code, too? Data only should be enough. > Really, I'd just map the EFI RT service virtual mappings "somewhere" > but at pgd[511] and have pgd[511] initially set up as > init_level4_pgt[511]. Then, thing should "just work"(TM). Nah, nothing with EFI just works :-) > If you fear the EFI code might do harm to the kernel code/data, then > you've lost anyway. Nothing will prevent the EFI code from doing nasty > things -- like setting up its own mappings to tamper with the kernel's > memory. Sure, nothing would surprise me anymore. However, I'd prefer to not be an enabler. :) -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/