Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753856AbcDYGi0 (ORCPT ); Mon, 25 Apr 2016 02:38:26 -0400 Received: from mail-wm0-f66.google.com ([74.125.82.66]:34879 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753787AbcDYGh5 (ORCPT ); Mon, 25 Apr 2016 02:37:57 -0400 From: Eric Engestrom To: linux-kernel@vger.kernel.org Cc: Eric Engestrom , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , x86@kernel.org, Jonathan Corbet , linux-doc@vger.kernel.org Subject: [PATCH 40/41] Documentation: x86: fix spelling mistakes Date: Mon, 25 Apr 2016 07:37:06 +0100 Message-Id: <1461566229-4717-14-git-send-email-eric@engestrom.ch> X-Mailer: git-send-email 2.8.0 In-Reply-To: <1461566229-4717-1-git-send-email-eric@engestrom.ch> References: <1461543878-3639-1-git-send-email-eric@engestrom.ch> <1461566229-4717-1-git-send-email-eric@engestrom.ch> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1411 Lines: 29 Signed-off-by: Eric Engestrom --- Documentation/x86/intel_mpx.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/x86/intel_mpx.txt b/Documentation/x86/intel_mpx.txt index 818518a..1a5a121 100644 --- a/Documentation/x86/intel_mpx.txt +++ b/Documentation/x86/intel_mpx.txt @@ -136,7 +136,7 @@ A: MPX-enabled application will possibly create a lot of bounds tables in If we were to preallocate them for the 128TB of user virtual address space, we would need to reserve 512TB+2GB, which is larger than the entire virtual address space today. This means they can not be reserved - ahead of time. Also, a single process's pre-popualated bounds directory + ahead of time. Also, a single process's pre-populated bounds directory consumes 2GB of virtual *AND* physical memory. IOW, it's completely infeasible to prepopulate bounds directories. @@ -151,7 +151,7 @@ A: This would work if we could hook the site of each and every memory these calls. Q: Could a bounds fault be handed to userspace and the tables allocated - there in a signal handler intead of in the kernel? + there in a signal handler instead of in the kernel? A: mmap() is not on the list of safe async handler functions and even if mmap() would work it still requires locking or nasty tricks to keep track of the allocation state there. -- 2.8.0