From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AD22CC43381 for ; Thu, 28 Feb 2019 11:45:38 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 759E72083D for ; Thu, 28 Feb 2019 11:45:38 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="jQtLvrwH"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=armh.onmicrosoft.com header.i=@armh.onmicrosoft.com header.b="ioVwFnf8" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 759E72083D Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=arm.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:Content-ID:In-Reply-To: References:Message-ID:Date:Subject:To:From:Reply-To:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=as2Iqo2uDVyOQLEdqjDb0I94uuRYWqMYM8Sf6dzGd5Y=; b=jQtLvrwHJEcqwc NZlGWpXAwqUR0faVNv4vbm0syYYOm7VmEyHq2n1GF74ufm+pDNufKuU11Ygly1AWmX+OmtmukgRv5 8/jKeZpASaKbC7PJaSzUjBR/Ah78ne4JMb+kxRLvR+xE5mk+11pPJjylDK6nU/O6yTxySwCdIEHRO 8Z8YZmLviJT97fpICqdaR76LZWDyFRkemRBz0cIJhYVR607Ig57UZ1X9jZc+/xoK6oWCeUpJaGwJE xTfQznGcc/oyJ4DoDLmRgjkumGb2GMpxfJxjr21ycl7sB//j4VDzKa1ZsFTeg6uoz5zllb54xNfsG InWiNUCqnILOw7bHQf3g==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1gzK88-00032S-QN; Thu, 28 Feb 2019 11:45:36 +0000 Received: from mail-eopbgr60052.outbound.protection.outlook.com ([40.107.6.52] helo=EUR04-DB3-obe.outbound.protection.outlook.com) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1gzK83-000324-4X for linux-arm-kernel@lists.infradead.org; Thu, 28 Feb 2019 11:45:34 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com; s=selector1-arm-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Dr/0uTIEamk+CSZ84pYJXCSKEzQxEwAq4fcehvA+nGk=; b=ioVwFnf8CVZxWlorRZ9HbodZgTouQGd1p47WifPqAWkmvDA9Qgbi+1ajdwnEt+pNjNzhhfRh3z2b9xd2PmQfyUTuHOcg7TWyYclMR2peilYcMB3KWA544hw8aYi4MyrAAJ0QyRutKAo7DeOLES4MRmX83lFf1vWOi9vX047jqdI= Received: from DB8PR08MB4105.eurprd08.prod.outlook.com (20.179.12.12) by DB8PR08MB4153.eurprd08.prod.outlook.com (20.179.8.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1643.21; Thu, 28 Feb 2019 11:45:28 +0000 Received: from DB8PR08MB4105.eurprd08.prod.outlook.com ([fe80::c84c:c3bf:a13e:423a]) by DB8PR08MB4105.eurprd08.prod.outlook.com ([fe80::c84c:c3bf:a13e:423a%4]) with mapi id 15.20.1643.019; Thu, 28 Feb 2019 11:45:28 +0000 From: Steve Capper To: Ard Biesheuvel Subject: Re: [PATCH 0/9] 52-bit kernel + user VAs Thread-Topic: [PATCH 0/9] 52-bit kernel + user VAs Thread-Index: AQHUx6w1oMh6myss70WSkOxz9gCxzKXnCbYAgAAJv4CAAAD2gIAAArwAgAAD2wCAAAuFAIAAJ5MAgAsUZICAAC7ZgIACgguAgAAM9YCAAAZ3AA== Date: Thu, 28 Feb 2019 11:45:28 +0000 Message-ID: <20190228114517.GA27853@capper-debian.cambridge.arm.com> References: <20190219124825.GH8501@fuggles.cambridge.arm.com> <20190219130138.GI8501@fuggles.cambridge.arm.com> <20190219135640.GA15458@capper-debian.cambridge.arm.com> <20190226173007.GA1553@capper-debian.cambridge.arm.com> <20190228103547.GA27721@capper-debian.cambridge.arm.com> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Mutt/1.10.1 (2018-07-13) x-originating-ip: [217.140.96.140] x-clientproxiedby: DM5PR18CA0057.namprd18.prod.outlook.com (2603:10b6:3:22::19) To DB8PR08MB4105.eurprd08.prod.outlook.com (2603:10a6:10:b0::12) authentication-results: spf=none (sender IP is ) smtp.mailfrom=Steve.Capper@arm.com; x-ms-exchange-messagesentrepresentingtype: 1 x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 9a34d57d-5cb1-4fa6-61d9-08d69d723bfc x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(4618075)(2017052603328)(7153060)(7193020); SRVR:DB8PR08MB4153; x-ms-traffictypediagnostic: DB8PR08MB4153: x-ms-exchange-purlcount: 1 nodisclaimer: True x-microsoft-exchange-diagnostics: 1; DB8PR08MB4153; 20:55RAvqN6SX4REHO0xAffk8xjINx8bbpsjpf325Z5vI5w0enpVNYTYsxjjyL0RP50L1tUCmHiRchHj/1oN1w+hdK/IpO9OnLClEFqxrDEdLjc/3yX36jDOEWeNu+CC88v0nH0nXjRdSvBkBQHXaiuO7yeOYd1W+TMxOv0tq0aw9c= x-microsoft-antispam-prvs: x-forefront-prvs: 0962D394D2 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(346002)(396003)(39860400002)(366004)(136003)(199004)(189003)(52116002)(26005)(66066001)(478600001)(186003)(14454004)(476003)(486006)(2906002)(71200400001)(72206003)(11346002)(256004)(14444005)(86362001)(229853002)(446003)(8936002)(966005)(8676002)(99286004)(3846002)(102836004)(44832011)(6116002)(386003)(68736007)(6506007)(6436002)(76176011)(53936002)(316002)(93886005)(105586002)(6916009)(25786009)(7736002)(305945005)(5660300002)(6512007)(54906003)(6486002)(4326008)(6306002)(53946003)(58126008)(1076003)(6246003)(561944003)(81166006)(97736004)(81156014)(71190400001)(33656002)(106356001)(30864003)(18370500001); DIR:OUT; SFP:1101; SCL:1; SRVR:DB8PR08MB4153; H:DB8PR08MB4105.eurprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: arm.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: vaK29vE1dDCOY22eeJjKzSFLbeYEmfZ9nLAFtvMh9HnlGkPMUX9GQfm0lss/zTeGFzkTMIRIuYZM2gIknHEvZ6DztlCBSLZ5gwWpfgHJmHNeYWl8mh6WSD+sGfJQvLaXVMIzFCo8/j+Bg9l3V1AftlcwouHHJ2prLa/RbjW7OdvarFZ6NT5p7RLzAMcbgEk/xg92sSRtk0+wkxi9veplzZeLV9D1vRYyahC3c3qLzBFxSMseCJzZj0CMqMRXlKGT++EzDnME3ZagYG9JYsKqsdN6oeLUxBMxoaIFOg0HRWER8Mw8G3ukSCpXrp0sgPGXez230VkMcsXuaphJDRmZxArB8Zkzl2C2FV+QkJPqvT49uKN73C0yQKCvSQGglIb1DO+sVUN+vcnWFYta7+dzsqUBgEYD6615oTz0gGcbL4I= Content-ID: <95B9910B2C6B134A9B3EA06C18AB0E40@eurprd08.prod.outlook.com> MIME-Version: 1.0 X-OriginatorOrg: arm.com X-MS-Exchange-CrossTenant-Network-Message-Id: 9a34d57d-5cb1-4fa6-61d9-08d69d723bfc X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Feb 2019 11:45:25.6727 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-id: f34e5979-57d9-4aaa-ad4d-b122a662184d X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB8PR08MB4153 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190228_034531_361900_3A17CFD1 X-CRM114-Status: GOOD ( 40.73 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "crecklin@redhat.com" , Marc Zyngier , Catalin Marinas , Will Deacon , nd , linux-arm-kernel Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Feb 28, 2019 at 12:22:09PM +0100, Ard Biesheuvel wrote: > On Thu, 28 Feb 2019 at 11:36, Steve Capper wrote: > > > > On Tue, Feb 26, 2019 at 09:17:49PM +0100, Ard Biesheuvel wrote: > > > On Tue, 26 Feb 2019 at 18:30, Steve Capper wrote: > > > > > > > > On Tue, Feb 19, 2019 at 05:18:18PM +0100, Ard Biesheuvel wrote: > > > > > On Tue, 19 Feb 2019 at 14:56, Steve Capper wrote: > > > > > > > > > > > > On Tue, Feb 19, 2019 at 02:15:26PM +0100, Ard Biesheuvel wrote: > > > > > > > On Tue, 19 Feb 2019 at 14:01, Will Deacon wrote: > > > > > > > > > > > > > > > > On Tue, Feb 19, 2019 at 01:51:51PM +0100, Ard Biesheuvel wrote: > > > > > > > > > On Tue, 19 Feb 2019 at 13:48, Will Deacon wrote: > > > > > > > > > > > > > > > > > > > > On Tue, Feb 19, 2019 at 01:13:32PM +0100, Ard Biesheuvel wrote: > > > > > > > > > > > On Mon, 18 Feb 2019 at 18:05, Steve Capper wrote: > > > > > > > > > > > > > > > > > > > > > > > > This patch series adds support for 52-bit kernel VAs using some of the > > > > > > > > > > > > machinery already introduced by the 52-bit userspace VA code in 5.0. > > > > > > > > > > > > > > > > > > > > > > > > As 52-bit virtual address support is an optional hardware feature, > > > > > > > > > > > > software support for 52-bit kernel VAs needs to be deduced at early boot > > > > > > > > > > > > time. If HW support is not available, the kernel falls back to 48-bit. > > > > > > > > > > > > > > > > > > > > > > > > A significant proportion of this series focuses on "de-constifying" > > > > > > > > > > > > VA_BITS related constants. > > > > > > > > > > > > > > > > > > > > > > > > In order to allow for a KASAN shadow that changes size at boot time, one > > > > > > > > > > > > must fix the KASAN_SHADOW_END for both 48 & 52-bit VAs and "grow" the > > > > > > > > > > > > start address. Also, it is highly desirable to maintain the same > > > > > > > > > > > > function addresses in the kernel .text between VA sizes. Both of these > > > > > > > > > > > > requirements necessitate us to flip the kernel address space halves s.t. > > > > > > > > > > > > the direct linear map occupies the lower addresses. > > > > > > > > > > > > > > > > > > > > > > > > One obvious omission is 52-bit kernel VA + 48-bit userspace VA which I > > > > > > > > > > > > can add with some more #ifdef'ery if needed. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi Steve, > > > > > > > > > > > > > > > > > > > > > > Apologies if I am bringing up things that have been addressed > > > > > > > > > > > internally already. We discussed the 52-bit kernel VA work at > > > > > > > > > > > plumber's at some point, and IIUC, KASAN is the complicating factor > > > > > > > > > > > when it comes to having compile time constants for VA_BITS_MIN, > > > > > > > > > > > VA_BITS_MAX and PAGE_OFFSET, right? > > > > > > > > > > > > > > > > > > > > > > To clarify what I mean, please refer to the diagram below, which > > > > > > > > > > > describes a hybrid 48/52 kernel VA arrangement that does not rely on > > > > > > > > > > > runtime variable quantities. (VA_BITS_MIN == 48, VA_BITS_MAX == 52) > > > > > > > > > > > > > > > > > > > > > > +------------------- (~0) -------------------------+ > > > > > > > > > > > | | > > > > > > > > > > > | PCI IO / fixmap spaces | > > > > > > > > > > > | | > > > > > > > > > > > +------------------------------------------------+ > > > > > > > > > > > | | > > > > > > > > > > > | kernel/vmalloc space | > > > > > > > > > > > | | > > > > > > > > > > > +------------------------------------------------+ > > > > > > > > > > > | | > > > > > > > > > > > | module space | > > > > > > > > > > > | | > > > > > > > > > > > +------------------------------------------------+ > > > > > > > > > > > | | > > > > > > > > > > > | BPF space | > > > > > > > > > > > | | > > > > > > > > > > > +------------------------------------------------+ > > > > > > > > > > > | | > > > > > > > > > > > | | > > > > > > > > > > > | vmemmap space (size based on VA_BITS_MAX) | > > > > > > > > > > > | | > > > > > > > > > > > | | > > > > > > > > > > > +-- linear/vmalloc split based on VA_BITS_MIN -- + > > > > > > > > > > > | | > > > > > > > > > > > | linear mapping (48 bit addressable region) | > > > > > > > > > > > | | > > > > > > > > > > > +------------------------------------------------+ > > > > > > > > > > > | | > > > > > > > > > > > | linear mapping (52 bit addressable region) | > > > > > > > > > > > | | > > > > > > > > > > > +------ PAGE_OFFSET based on VA_BITS_MAX --------+ > > > > > > > > > > > > > > > > > > > > > > Since KASAN is what is preventing this, would it be acceptable for > > > > > > > > > > > KASAN to only be supported when you use a true 48 bit or a true 52 bit > > > > > > > > > > > configuration, and disable it for the 48/52 hybrid configuration? > > > > > > > > > > > > > > > > > > > > > > Just thinking out loud (and in ASCII art :-)) > > > > > > > > > > > > > > > > > > > > TBH, if we end up having support for 52-bit kernel VA, I'd be inclined to > > > > > > > > > > drop the 48/52 configuration altogether. But Catalin's on holiday at the > > > > > > > > > > moment, and may have a different opinion ;) > > > > > > > > > > > > > > > > > > > > > > > > > > > > But that implies that you cannot have an image that supports 52-bit > > > > > > > > > kernel VAs but can still boot on hardware that does not implement > > > > > > > > > support for it. If that is acceptable, then none of this hoop jumping > > > > > > > > > that Steve is doing in these patches is necessary to begin with, > > > > > > > > > right? > > > > > > > > > > > > > > > > Sorry, I misunderstood what you meant by a "48/52 hybrid configuration". I > > > > > > > > thought you were referring to the configuration where userspace is 52-bit > > > > > > > > and the kernel is 48-bit, which is something I think we can drop if we gain > > > > > > > > support for 52-bit kernel. > > > > > > > > > > > > > > > > Now that I understand what you mean, I think disabling KASAN would be fine > > > > > > > > as long as it's a runtime thing and the kernel continues to work in every > > > > > > > > other respect. > > > > > > > > > > > > > > > > > > > > > > No, it would be a limitation of the 52-bit config which also supports > > > > > > > 48-bit-VA-only-h/w that the address space is laid out in such a way > > > > > > > that there is simply no room for the KASAN shadow region, since it > > > > > > > would have to live in the 48-bit addressable area, but be big enough > > > > > > > to cover 52 bits of VA, which is impossible. > > > > > > > > > > > > > > For the vmemmap space, we could live with sizing it statically to > > > > > > > cover a 52-bit VA linear region, but the KASAN shadow region is simply > > > > > > > too big. > > > > > > > > > > > > > > So if KASAN support in that configuration is a requirement, then I > > > > > > > agree with Steve's approach, but it does imply that quite a number of > > > > > > > formerly compile-time constants now get turned into runtime variables. > > > > > > > > > > > > > > Steve, do you have any idea what the impact of that is? > > > > > > > > > > > > Hi Guys, > > > > > > > > > > > > The KASAN region only really necessitates two things: 1) that we think > > > > > > about the end address of the region (which is invariant) rather than the > > > > > > start address; and that 2) we flip the kernel VA space. IIUC both these > > > > > > changes have a neglible perf impact. > > > > > > > > > > > > As for VA_BITS_ACTUAL, we need this in a few places: KVM mapping > > > > > > support, and the big one phys_to/from_virt. For phys_to/from_virt the > > > > > > logic is changed s.t. we use a variable lookup for translation but this > > > > > > is folded into a new variable physvirt_offset (before the patch we used > > > > > > a single variable read too). > > > > > > > > > > > > Again IIUC there should be a minimal perf impact (unless one tries to do > > > > > > cat /sys/kernel/debug/kernel_page_tables with KASAN enabled - but that > > > > > > can be optimised later). > > > > > > > > > > > > I didn't have the patience for ASCII art ;-), but I have a picture of > > > > > > what I think it looks like here: > > > > > > https://s3.amazonaws.com/connect.linaro.org/yvr18/presentations/yvr18-119.pdf > > > > > > What I've tried to do is have most parts of the kernel VA space > > > > > > invariant between 48/52 bits. If it's helpful I can type this up into a > > > > > > document/commit log message? > > > > > > > > > > > > For this series I have tried to introduce VA_BITS_MIN in its own patch > > > > > > and also VA_BITS_ACTUAL into its own patch to make it easier to follow. > > > > > > > > > > > > > > Hi Ard, > > > > > > > > Apologies for my late reply, I had been staring at this for a while. > > > > > > > > > > > > > > OK, perhaps I am just rephrasing what you essentially implemented > > > > > already, but let me try to explain a bit better what I mean: > > > > > > > > > > - we flip the VA space in the way you suggest > > > > > - we limit the size of the top half of the address space to 47 bits > > > > > - KASAN region growns downwards from (~0) << 47 > > > > > - we define PAGE_OFFSET as (~0) << 52, regardless of whether the h/w > > > > > supports LVA or not > > > > > - however, we tweak the phys/virt translation so that memory appears > > > > > in the 48-bit addressable part of the linear region on non-LVA > > > > > hardware > > > > > > > > > > The latter basically means that the KASAN shadow region will intersect > > > > > the linear region, but whether we map memory or shadow pages there > > > > > depends on the h/w config at runtime. > > > > > > > > > > The heart of the matter is probably the different placement of the > > > > > memory inside the linear region, depending on whether the h/w is LVA > > > > > capable or not, which is also reflected in your physvirt_offset. I am > > > > > just trying to figure out why we need VA_BITS_ACTUAL to be a runtime > > > > > variable. > > > > > > > > Currently the direct linear map between configurations does not overlap, > > > > we have: > > > > > > > > FFF00000_00000000 - Direct linear map start (52-bit) > > > > FFF80000_00000000 - Direct linear map end (52-bit) > > > > FFFF0000_00000000 - Direct linear map start (48-bit) > > > > FFFF8000_00000000 - Direct linear map end (48-bit) > > > > > > > > We *can* make PAGE_OFFSET a constant for both 48/52 bit VA_BITS, if we > > > > offset it. vmemmap can then be adjusted on early boot to ensure that > > > > everything points to the right place. However we will get overlap for > > > > 52-bit configurations between KASAN and the direct linear map. > > > > > > > > The question is: are we okay with quite a large overlap? > > > > > > > > The KASAN region begins on 0xFFFDA000_00000000 for 52-bit. If we wish to > > > > employ a "full" 47-bit direct linear map on 48-bit systems we need a > > > > PAGE_OFFSET of 0xFFF78000_00000000 in order to make the direct linear > > > > map end addresses "match up" between 48/52 bit configurations. > > > > > > > > This doesn't leave us with a lot of room for 52-bit configurations > > > > though, if KASAN is enabled. > > > > > > > > > > OK, so with actual numbers, what I had in mind was > > > > > > > > > FFF00000_00000000 start of 52-bit addressable linear region | PAGE_OFFSET > > > > > > FFFD8000_00000000 start of KASAN shadow region | KASAN_SHADOW_OFFSET > > > > > > FFFF0000_00000000 start of 48-bit addressable linear region > > > > > > FFFF6000_00000000 start of used KASAN shadow region (48-bit VA) > > > (KASAN_SHADOW_OFFSET + F0000_00000000 >> 3) > > > > > > FFFF8000_00000000 start of vmemmap area - end of KASAN shadow region > > > > > > FFFF8200_00000000 end of vmemmap area - start of bpf/module/etc area > > > > > > > > > The trick is that the full (52 - 3) bits KASAN shadow space overlaps > > > with the 48-bit linear region, but since you don't need KASAN shadow > > > pages for memory that does not exist, the region FFFF0000_00000000 - > > > FFFF6000_00000000 can be used for mapping the memory in case the h/w > > > is 48-bit only. > > > > > > So in this case, PAGE_OFFSET and KASAN_SHADOW_OFFSET remain compile > > > time constants, and as long as we don't attempt to map anything > > > outside of the 48-bit addressable area on h/w that does not support > > > it, the fact that those quantities are outside the 48-bit range does > > > not really matter. > > > > Thanks Ard, > > I'll elaborate more on what I'm worrying about :-). > > > > The 48/52 bit linear regions above do not overlap and this creates the > > following issue. > > > > OK, I see what you mean (I think). In my proposal, the linear regions > *do* overlap. > > In my example, the vmemmap region is only sized to cover 51 bits of > linear region, but this is not sufficient, since the 52-bit linear > region is actually bigger than that. > Ahhhh, okay, nice (sorry I didn't parse your numbers correctly before). > So based on a linear region that goes from > > FFF0_0000_0000_0000 ... FFFF_8000_0000_0000 > > we would end up with a vmemmap region > > FFFF_8000_0000_0000 ... FFFF_83E0_0000_0000 > > covering the entire combined linear region. This is a fair chunk of > the vmalloc space for 48-bit configuration, but I don't think that is > anything to worry about. > > > To go from a struct page * to a linear address we do the following: > > lva = (page - VMEMMAP_START) * PAGE_SIZE / sizeof(struct page) + PAGE_OFFSET > > > > OK, so given the above correction, we can take > > VMEMMAP_START := FFFF_8000_0000_0000 > PAGE_OFFSET := FFF0_0000_0000_0000 > > and everything still adds up afaict, and struct pages in the 48-bit VA > region are covered from FFFF_83C0_0000_0000 and up. > > > (Before my series) all the constants are fixed at compile time and thus > > translation is very quick. My understanding is that you would like > > PAGE_OFFSET to be constant to preserve the optimised nature of this > > transform? (if not, please shout :-) ) > > > > Yes, the main idea is to have compile time constants for PAGE_OFFSET, > VA_BITS, etc > > > The problem is that a 52-bit PAGE_OFFSET = 0xFFF00000_00000000 will > > never be able to give us an lva within a 48-bit addressable range. At > > best we will get an lva of FFF80000_00000000. > > > > You are assuming that we have to split the address space down the > middle, but I don't think that is necessary at all. > Agreed, some minor tweaks are needed to some helper functions to allow for this. Many thanks Ard, I'll give this a go. Cheers, -- Steve _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel