From: "atul srivastava" <atulsrivastava9@rediffmail.com>
To: "Ralf Baechle" <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: Re: watch exception only for kseg0 addresses..?
Date: 25 Nov 2002 10:01:52 -0000 [thread overview]
Message-ID: <20021125100152.6471.qmail@mailweb33.rediffmail.com> (raw)
>
> > in change history of this file i am able to see KSEG0
>restriction
> > removed only for arch/mips64/lib/watch.S...
>
>The hw takes physical addresses, so using a a virtual address as
>argument >for __watch_set seemed to be stupid anyway. The hw
>takes a physical address and the conversion is best done in C
>anyway.
>The whole watch stuff in the the kernel is pretty much an ad-hoc
>API
>which I did create to debug a stack overflow. I'm sure if
>you're
>going to use it you'll find problems. For userspace for example
>you'd
>have to switch the watch register when switching the MMU context
>so
>each process gets it's own virtual watch register.
Beyond that there
>are at least two different formats of watch registers implemented
>in
>actual silicon, the original R4000-style and the MIPS32/MIPS64
>style
>watch registers and the kernel's watch code only know the R4000
>style
my cpu manual ( IDT RC32334) talks about two watch registers
CP0_IWATCH and CP0_DWATCH where it is required to just put desired
VIRTUAL( bits 2--31) addresses to be watched , there is no mention
of CP0_WATCHLO and CP0_WATCHHI .
additionally i guees for userspace virtual watch register problem,
the hardware takes care of all , i just need to specify my virual
address this is what i understand from my manual.
and one more problem i face when i try to debug a mysterious page
fault problem, that i get my watch exception but after page fault
..hence I can't really debug , shouldn't the priority of watch
exceptions should be higher than atleast instruction fetch
exception.? or the scope of debugging by watch exception is
limited by design.....
next reply other threads:[~2002-11-25 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-25 10:01 atul srivastava [this message]
2002-11-25 10:41 ` Re: watch exception only for kseg0 addresses..? Ralf Baechle
2002-11-25 12:04 ` Kevin D. Kissell
2002-11-25 12:04 ` Kevin D. Kissell
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=20021125100152.6471.qmail@mailweb33.rediffmail.com \
--to=atulsrivastava9@rediffmail.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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