From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56201) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z4Tkd-0000Ux-Vp for qemu-devel@nongnu.org; Mon, 15 Jun 2015 08:44:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z4Tka-000642-Nq for qemu-devel@nongnu.org; Mon, 15 Jun 2015 08:44:31 -0400 Received: from mail-yk0-f177.google.com ([209.85.160.177]:36188) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z4Tka-00063c-D3 for qemu-devel@nongnu.org; Mon, 15 Jun 2015 08:44:28 -0400 Received: by ykaz81 with SMTP id z81so55097990yka.3 for ; Mon, 15 Jun 2015 05:44:27 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: Peter Maydell Date: Mon, 15 Jun 2015 13:44:07 +0100 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [PATCH target-arm v2 04/13] arm: Refactor get_phys_addr FSR return mechanism List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Crosthwaite Cc: Edgar Iglesias , jues@xilinx.com, QEMU Developers , Zach Pfeffer , Alistair Francis On 12 June 2015 at 20:10, Peter Crosthwaite wrote: > Currently, the return code for get_phys_addr is overloaded for both > success/fail and FSR value return. This doesn't handle the case where > there is an error with a 0 FSR. This case exists in PMSAv7. > > So rework get_phys_addr and friends to return a success/failure boolean > return code and populate the FSR via a caller provided uint32_t > pointer. true-on-failure, false-on-success is an odd way round for a success/failure bool, but I guess it keeps the rest of the code from changing too much... -- PMM