From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751483AbdKUVUD (ORCPT ); Tue, 21 Nov 2017 16:20:03 -0500 Received: from mga01.intel.com ([192.55.52.88]:43894 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751263AbdKUVUA (ORCPT ); Tue, 21 Nov 2017 16:20:00 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,432,1505804400"; d="scan'208";a="7992743" Subject: Re: [PATCH 12/30] x86, kaiser: map GDT into user page tables To: Andy Lutomirski , Thomas Gleixner References: <20171110193058.BECA7D88@viggo.jf.intel.com> <20171110193125.EBF58596@viggo.jf.intel.com> Cc: "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , moritz.lipp@iaik.tugraz.at, Daniel Gruss , michael.schwarz@iaik.tugraz.at, richard.fellner@student.tugraz.at, Linus Torvalds , Kees Cook , Hugh Dickins , X86 ML From: Dave Hansen Message-ID: Date: Tue, 21 Nov 2017 13:19:57 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/20/2017 12:46 PM, Andy Lutomirski wrote: >>> + /* >>> + * We could theoretically do this in setup_fixmap_gdt(). >>> + * But, we would need to rewrite the above page table >>> + * allocation code to use the bootmem allocator. The >>> + * buddy allocator is not available at the time that we >>> + * call setup_fixmap_gdt() for CPU 0. >>> + */ >>> + kaiser_add_user_map_early(get_cpu_gdt_ro(0), PAGE_SIZE, >>> + __PAGE_KERNEL_RO | _PAGE_GLOBAL); >> This one is needs to stay. > When you rebase on to my latest version, this should change to mapping > the entire cpu_entry_area. I did this, but unfortunately it ends up having to individually map all four pieces of cpu_entry_area. They all need different permissions and while theoretically we could do TSS+exception-stacks in the same call, they're not next to each other: GDT: R/O TSS: R/W at least because of trampoline stack entry code: EXEC+R/O exception stacks: R/W