public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Phil Muldoon <pmuldoon@redhat.com>, frysk@sourceware.org
Subject: Re: fstep added
Date: Mon, 22 Jan 2007 19:00:00 -0000	[thread overview]
Message-ID: <45B509C5.2000908@redhat.com> (raw)
In-Reply-To: <1169482750.29512.1.camel@hermans.wildebeest.org>

Unfortunatly current kernels don't allow mmapping of /proc/PID/maps; 
however open/pread works.

Andrew

Mark Wielaard wrote:
> On Mon, 2007-01-22 at 07:51 -0600, Phil Muldoon wrote: 
>   
>> Resurrecting this thread for a little bit. Is this issue related to:
>>
>> http://sourceware.org/bugzilla/show_bug.cgi?id=3727
>>
>> I'm hazarding a guess this all comes down to ptrace accessing the 
>> inferior's memory word by word, and that optimizations made in access to 
>> the inferior's memory (ie by mmaping /proc/$$/memory) will benefit fcore 
>> as well as fstep? My knowledge here is really fuzzy.
>>     
>
> Yes and http://sourceware.org/bugzilla/show_bug.cgi?id=3761 which are
> basically the same issue. To speedup fstep and fcore) we would like to
> mmap /proc/<pid>/mem for the inferior and wrap it in an inua ByteBuffer.
> This doesn't provide write access, but we do reads mostly anyway. You
> can imagine a ByteBuffer returned by Task.getMemory() that delegates
> reads through such an mmap backed inua ByteBuffer and writes delegated
> through a ptrace backed inua ByteBuffer.
>
> Cheers,
>
> Mark
>
>   

      reply	other threads:[~2007-01-22 19:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-18 14:01 Mark Wielaard
2006-12-18 16:05 ` Andrew Cagney
2006-12-18 19:41   ` Mark Wielaard
2007-01-22 13:52   ` Phil Muldoon
2007-01-22 16:19     ` Mark Wielaard
2007-01-22 19:00       ` Andrew Cagney [this message]

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=45B509C5.2000908@redhat.com \
    --to=cagney@redhat.com \
    --cc=frysk@sourceware.org \
    --cc=mark@klomp.org \
    --cc=pmuldoon@redhat.com \
    /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).