From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753854AbcBXQUL (ORCPT ); Wed, 24 Feb 2016 11:20:11 -0500 Received: from mail.skyhub.de ([78.46.96.112]:52953 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757358AbcBXQUG (ORCPT ); Wed, 24 Feb 2016 11:20:06 -0500 Date: Wed, 24 Feb 2016 17:20:02 +0100 From: Borislav Petkov To: Matt Fleming , Andy Lutomirski Cc: Sai Praneeth Prakhya , "Ravi V. Shankar" , Toshi Kani , Brian Gerst , Thomas Gleixner , Ingo Molnar , Linus Torvalds , Luis Rodriguez , Andrew Morton , Denys Vlasenko , "H. Peter Anvin" , "linux-kernel@vger.kernel.org" , Peter Zijlstra , ricardo.neri@intel.com, Hugh Dickins , Ard Biesheuvel Subject: Re: [tip:efi/core] x86/mm/pat: Use _PAGE_GLOBAL bit for EFI page table mappings Message-ID: <20160224162002.GE3888@pd.tnic> References: <1455712566-16727-4-git-send-email-matt@codeblueprint.co.uk> <1456275002.2781.41.camel@intel.com> <20160224141046.GA2603@codeblueprint.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20160224141046.GA2603@codeblueprint.co.uk> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 24, 2016 at 02:10:46PM +0000, Matt Fleming wrote: > > Normally, the only pages with are _PAGE_GLOBAL are those that are in > > the normal kernel mappings (swapper_pg_dir and normal mm_struct pgds). > > By allowing _PAGE_GLOBAL to be set in EFI mappings, you're breaking > > that convention, which forces you to use extra-expensive > > __flush_tlb_all calls in efi_call_virt. Hold on, do you mean the __flush_tlb_all() in the CONFIG_EFI_MIXED code? That's mixed mode. I think you mean the FLUSH_TLB_ALL in efi_call. That's EFI on 64-bit but that is mandated by the spec, AFAIR. So the EFI runtime crap should not change once it is mapped. And those should be global. It is only natural. > Nope. The "if (cpa->pgd)" guard ensures that we only call that > function for the EFI mapping code - no one else sets ->pgd. But it could - there's no guarantee. kernel_map_pages_in_pgd() is an exported facility. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply.