From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Brook Subject: Re: [Qemu-devel] Re: [PATCH 2/6] Use correct types to enable > 2G support (v2) Date: Sun, 10 Feb 2008 14:59:32 +0000 Message-ID: <200802101459.33683.paul@codesourcery.com> References: <1201903921-1125-1-git-send-email-aliguori@us.ibm.com> <200802101412.27850.paul@codesourcery.com> <47AF104C.3060401@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org To: Avi Kivity Return-path: In-Reply-To: <47AF104C.3060401@qumranet.com> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org On Sunday 10 February 2008, Avi Kivity wrote: > Paul Brook wrote: > >>> as far as i remember it was used to address something with > >>> cpu_physical_memory_rw() probably related to &TARGET_PAGE_SIZE > >>> or ~TARGET_PAGE_SIZE, > >>> > >>> the fact is that i dont know if it ever fixed anything > >> > >> It fixes TARGET_PAGE_MASK, defined one line downscreen. > > > > That doesn't really answer the question. What was wrong with the original > > definition? > > There are many instances of ((physical address) & TARGET_PAGE_MASK) > scattered throughout the code. With 64-bit physical addresses, this > causes truncation. No it doesn't. TARGET_PAGE_MASK will be sign extended to the width of physical_address. This is why I asked for a concrete example of something that broke. Paul ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/