public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: frysk <frysk@sourceware.org>
Subject: Re: [patch] LogicalMemoryBuffer
Date: Fri, 03 Aug 2007 14:03:00 -0000	[thread overview]
Message-ID: <46B335A4.6020503@redhat.com> (raw)
In-Reply-To: <1186053948.15044.61.camel@dijkstra.wildebeest.org>

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

  reply	other threads:[~2007-08-03 14:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-20 12:02 Mark Wielaard
2007-07-30 12:42 ` Mark Wielaard
2007-08-02 11:26 ` Mark Wielaard
2007-08-03 14:03   ` Phil Muldoon [this message]
2007-08-06  9:17     ` Mark Wielaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46B335A4.6020503@redhat.com \
    --to=pmuldoon@redhat.com \
    --cc=frysk@sourceware.org \
    --cc=mark@klomp.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).