From: "Kevin D. Kissell" <kevink@mips.com>
To: "atul srivastava" <atulsrivastava9@rediffmail.com>,
"Ralf Baechle" <ralf@linux-mips.org>
Cc: <linux-mips@linux-mips.org>
Subject: Re: Re: watch exception only for kseg0 addresses..?
Date: Mon, 25 Nov 2002 13:04:28 +0100 [thread overview]
Message-ID: <00d001c2947a$d71231d0$10eca8c0@grendel> (raw)
In-Reply-To: 20021125100152.6471.qmail@mailweb33.rediffmail.com
> > 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 .
Your CPU would appear to be neither MIPS32/MIPS64 compliant
nor R4000 backward-compatible. The designers may have sought
to simplify the use of watch registers in user space, apparently at the price
of the restriction you are seeing.
> 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.....
Does your CPU implement EJTAG?
Kevin K.
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: atul srivastava <atulsrivastava9@rediffmail.com>,
Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: Re: watch exception only for kseg0 addresses..?
Date: Mon, 25 Nov 2002 13:04:28 +0100 [thread overview]
Message-ID: <00d001c2947a$d71231d0$10eca8c0@grendel> (raw)
Message-ID: <20021125120428.piDSbXZwLJoGjlUbnMmor2N4aw3Rh0UytHEVoktZU30@z> (raw)
In-Reply-To: 20021125100152.6471.qmail@mailweb33.rediffmail.com
> > 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 .
Your CPU would appear to be neither MIPS32/MIPS64 compliant
nor R4000 backward-compatible. The designers may have sought
to simplify the use of watch registers in user space, apparently at the price
of the restriction you are seeing.
> 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.....
Does your CPU implement EJTAG?
Kevin K.
next prev parent reply other threads:[~2002-11-25 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-25 10:01 Re: watch exception only for kseg0 addresses..? atul srivastava
2002-11-25 10:41 ` Ralf Baechle
2002-11-25 12:04 ` Kevin D. Kissell [this message]
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='00d001c2947a$d71231d0$10eca8c0@grendel' \
--to=kevink@mips.com \
--cc=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