From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753074AbbJ0VJM (ORCPT ); Tue, 27 Oct 2015 17:09:12 -0400 Received: from mail-wi0-f179.google.com ([209.85.212.179]:34492 "EHLO mail-wi0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751902AbbJ0VIu (ORCPT ); Tue, 27 Oct 2015 17:08:50 -0400 Date: Tue, 27 Oct 2015 21:08:47 +0000 From: Matt Fleming To: Ard Biesheuvel Cc: Taku Izumi , Ingo Molnar , "linux-kernel@vger.kernel.org" , kamezawa.hiroyu@jp.fujitsu.com, "linux-efi@vger.kernel.org" Subject: Re: [PATCH v2] efi: Fix warning of int-to-pointer-cast on x86 32-bit builds Message-ID: <20151027210847.GB8973@codeblueprint.co.uk> References: <1445593826-4578-1-git-send-email-izumi.taku@jp.fujitsu.com> <20151026210235.GA3526@codeblueprint.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 Tue, 27 Oct, at 11:33:55AM, Ard Biesheuvel wrote: > > Does UEFI even allow that? Even if it can describe memory over 4 GB, > it uses a flat mapping so allocations done by the stub (which > retrieves the memory map) should never reside at addresses over 4 GB. Right, exactly. We're good with phys_addr_t. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Fleming Subject: Re: [PATCH v2] efi: Fix warning of int-to-pointer-cast on x86 32-bit builds Date: Tue, 27 Oct 2015 21:08:47 +0000 Message-ID: <20151027210847.GB8973@codeblueprint.co.uk> References: <1445593826-4578-1-git-send-email-izumi.taku@jp.fujitsu.com> <20151026210235.GA3526@codeblueprint.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-efi-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Ard Biesheuvel Cc: Taku Izumi , Ingo Molnar , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org, "linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" List-Id: linux-efi@vger.kernel.org On Tue, 27 Oct, at 11:33:55AM, Ard Biesheuvel wrote: > > Does UEFI even allow that? Even if it can describe memory over 4 GB, > it uses a flat mapping so allocations done by the stub (which > retrieves the memory map) should never reside at addresses over 4 GB. Right, exactly. We're good with phys_addr_t.