From: Andrew Cagney <ac131313@redhat.com>
To: gdb@sources.redhat.com
Subject: Known problems with dcache?
Date: Fri, 10 Jan 2003 22:19:00 -0000 [thread overview]
Message-ID: <3E1F46CB.9060104@redhat.com> (raw)
Hello,
In a recent discussion there was mention made of dcache. How, when
enabled, it could make things? Are there any more details.
The only problem I know with dcache is with the way it turns a single
byte read into a 32 byte read. I think it should instead behave like a
register fetch:
- request exactly the specified amount
- allow the target to supply additional data
ex: ask for a byte, get back a page.
I even think that, with that fix, the dcache could be enabled by default
- it couldn't accidently do things like read beyond the end of memory
and in the process trash something for instance.
Andrew
PS: Thinking about it, given ptrace's 4 byte straw, 32 bytes ~= 8 ptrace
calls and that could be enough to make a difference?
next reply other threads:[~2003-01-10 22:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 22:19 Andrew Cagney [this message]
2003-01-10 22:25 ` Daniel Jacobowitz
2003-01-10 22:36 ` Andrew Cagney
2003-01-10 22:38 ` Daniel Jacobowitz
2003-01-10 22:55 ` Andrew Cagney
2003-01-10 23:04 ` Daniel Jacobowitz
2003-01-10 23:16 ` Andrew Cagney
2003-01-10 23:21 ` Daniel Jacobowitz
2003-01-11 17:52 ` Andrew Cagney
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=3E1F46CB.9060104@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.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