From: Ralf Baechle <ralf@uni-koblenz.de>
To: "Vladimir A. Roganov" <roganov@niisi.msk.ru>
Cc: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr,
linux-mips@vger.rutgers.edu
Subject: Re: Platform-independent hack in ptrace.c
Date: Sat, 29 May 1999 16:51:47 +0200 [thread overview]
Message-ID: <19990529165147.B1517@uni-koblenz.de> (raw)
In-Reply-To: <374E5FB1.D3860089@niisi.msk.ru>; from Vladimir A. Roganov on Fri, May 28, 1999 at 01:19:45PM +0400
On Fri, May 28, 1999 at 01:19:45PM +0400, Vladimir A. Roganov wrote:
> We implemented it by very interesting reason: old Baget uses special
> VIC register which exists on bus only (!!!) when interrupt is active.
> But interrupt can be deactivated by external reason. In such case
> IRQ handler catch SIGBUS, what crashes current process.
>
> It was overwritten twice, and it looks debugged hardly :-)
> May be it can help here.
>
> > The other bug is that memory accesses via ptrace for virtual addresses
> > which are uncached would be executed cached, trouble ahead.
>
> YES, we obtained such effect.
> To avoid it we just moved to physical address space (high bits are ignored),
> but it is not good in general.
>
> > Further complexity is added by handling write buffers for the R3000 and
> > virtual coherency for R4000.
>
> Yes, it should be tried to be fixed once for every arch.
That means we need something like read_phys() and write_phys() for all
CPU variants, even board variations. The functions needs to get passed
an virtual address as well such that it can deal with virtual coherency
on R4000.
Then again R10k does this in hardware, so why bother ;-)
Ralf
prev parent reply other threads:[~1999-05-29 23:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <374D37E6.59A6A9F3@niisi.msk.ru>
1999-05-27 19:26 ` Platform-independent hack in ptrace.c Ralf Baechle
[not found] ` <374E5FB1.D3860089@niisi.msk.ru>
1999-05-29 14:51 ` Ralf Baechle [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=19990529165147.B1517@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@vger.rutgers.edu \
--cc=linux@cthulhu.engr.sgi.com \
--cc=roganov@niisi.msk.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.