From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24097 invoked by alias); 3 Aug 2007 14:03:29 -0000 Received: (qmail 24084 invoked by uid 22791); 3 Aug 2007 14:03:27 -0000 X-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,DK_POLICY_SIGNSOME,FORGED_RCVD_HELO,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 03 Aug 2007 14:03:23 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l73E3JwF024819; Fri, 3 Aug 2007 10:03:19 -0400 Received: from pobox.hsv.redhat.com (pobox.hsv.redhat.com [172.16.16.12]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l73E3IUe005431; Fri, 3 Aug 2007 10:03:18 -0400 Received: from localhost.localdomain (vpn-14-158.rdu.redhat.com [10.11.14.158]) by pobox.hsv.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id l73E3HmQ031699; Fri, 3 Aug 2007 10:03:17 -0400 Message-ID: <46B335A4.6020503@redhat.com> Date: Fri, 03 Aug 2007 14:03:00 -0000 From: Phil Muldoon User-Agent: Thunderbird 2.0.0.5 (X11/20070719) MIME-Version: 1.0 To: Mark Wielaard CC: frysk Subject: Re: [patch] LogicalMemoryBuffer References: <1184932926.3611.58.camel@dijkstra.wildebeest.org> <1186053948.15044.61.camel@dijkstra.wildebeest.org> In-Reply-To: <1186053948.15044.61.camel@dijkstra.wildebeest.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2007-q3/txt/msg00265.txt.bz2 Mark Wielaard wrote: > Hi, > > On Fri, 2007-07-20 at 14:02 +0200, Mark Wielaard wrote: > >> - LogicalMemoryBuffer is a filter on top of AddressSpaceByteBuffer but >> really should be on top of MemorySpaceByteBuffer which is more >> effecient. The used to be interface compatible, but a recent change to >> MemorySpaceByteBuffer changed that and made that it less easy to wrap. >> MemorySpaceByteBuffer is really just an optimization of >> AddressSpaceByteBuffer (in the case of AddressSpace.TEXT/DATA) and all >> code should go through the optimized path (StateLessFile) for accessing >> memory if the AddressSpace allows it. So I am going to merge the two >> (and fix up the places that currently use the slow path). Then I'll also >> add the ByteBuffer.get() optimization that Chris pointed out. >> Can you write up the difference between Logical and Raw Memory? How is Raw memory exported? If a break-point has been added to memory 0x123434 is the map marked as written in RawMemory? Regards Phil