From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751587AbdKUWMn (ORCPT ); Tue, 21 Nov 2017 17:12:43 -0500 Received: from mga09.intel.com ([134.134.136.24]:63111 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751439AbdKUWMm (ORCPT ); Tue, 21 Nov 2017 17:12:42 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,432,1505804400"; d="scan'208";a="8011701" Subject: Re: [PATCH 12/30] x86, kaiser: map GDT into user page tables To: 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@iaik.tugraz.at, michael.schwarz@iaik.tugraz.at, richard.fellner@student.tugraz.at, luto@kernel.org, torvalds@linux-foundation.org, keescook@google.com, hughd@google.com, x86@kernel.org From: Dave Hansen Message-ID: <6f13e451-c333-d966-4169-ccda7a02ae06@linux.intel.com> Date: Tue, 21 Nov 2017 14:12:40 -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:22 PM, Thomas Gleixner wrote: > On Fri, 10 Nov 2017, Dave Hansen wrote: >> __set_fixmap(get_cpu_gdt_ro_index(cpu), get_cpu_gdt_paddr(cpu), prot); >> + >> + /* CPU 0's mapping is done in kaiser_init() */ >> + if (cpu) { >> + int ret; >> + >> + ret = kaiser_add_mapping((unsigned long) get_cpu_gdt_ro(cpu), >> + PAGE_SIZE, __PAGE_KERNEL_RO); >> + /* >> + * We do not have a good way to fail CPU bringup. >> + * Just WARN about it and hope we boot far enough >> + * to get a good log out. >> + */ > > The GDT fixmap can be set up before the CPU is started. There is no reason > to do that in cpu_init(). Do you mean the __set_fixmap(), or my call to kaiser_add_mapping()? Where would you suggest we move it? Here seems kinda nice because it's right next to where the get_cpu_gdt_ro() mapping is created.