From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Daniel Jacobowitz <dan@debian.org>,
atul srivastava <atulsrivastava9@rediffmail.com>,
linux-mips@linux-mips.org
Subject: Re: watch exception only for kseg0 addresses..?
Date: Wed, 4 Dec 2002 01:37:13 +0100 [thread overview]
Message-ID: <20021204013713.D18419@linux-mips.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1021125163423.8769I-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Mon, Nov 25, 2002 at 04:47:33PM +0100
On Mon, Nov 25, 2002 at 04:47:33PM +0100, Maciej W. Rozycki wrote:
> > MIPS64 extends that to also support instruction address matches; the
> > granularity can be set anywhere from 8 bytes to 4kB; in addition ASID
> > matching and a global bit can be used for matching. A MIPS64 CPU can
> > support anywhere from 0 to 4 such watch registers.
>
> Actually up to eight -- for all dmfc0/dmtc0 3-bit "sel" values, if I read
> it correctly.
Correct but I don't know of any CPU that actually uses more than 4 of the
possible 8 sets atm. So we're both right :)
> > The global bit stuff would only be useful for in-kernel use, I think. The
> > ASID thing could be used to implement watchpoints for an entire process, not
> > just per thread though I doubt there is much use for something like that.
>
> Well, there are two options only -- either use global matching or ASID
> matching. What else would you expect? Do you mean lazy vs immediate
> switching?
Basically there would be two possibilities, associate the debugging state
of a process with it's thread_struct or with it's mm_struct. The latter
would have a little less impact on the context switching performance,
the first be a bit more flexible.
Ralf
next prev parent reply other threads:[~2002-12-04 0:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-25 7:52 watch exception only for kseg0 addresses..? atul srivastava
2002-11-25 9:24 ` Ralf Baechle
2002-11-25 11:55 ` Maciej W. Rozycki
2002-11-25 12:18 ` Ralf Baechle
2002-11-25 14:40 ` Daniel Jacobowitz
2002-11-25 15:08 ` Ralf Baechle
2002-11-25 15:47 ` Maciej W. Rozycki
2002-12-04 0:37 ` Ralf Baechle [this message]
2002-12-04 0:58 ` Daniel Jacobowitz
2002-12-04 15:48 ` Maciej W. Rozycki
2002-11-25 15:30 ` Maciej W. Rozycki
2002-12-04 0:15 ` Daniel Jacobowitz
2002-12-04 15:45 ` Maciej W. Rozycki
2002-12-04 15:51 ` Daniel Jacobowitz
2002-12-04 17:54 ` Maciej W. Rozycki
2002-12-11 16:58 ` Daniel Jacobowitz
2002-12-11 17:38 ` Maciej W. Rozycki
2002-12-11 18:01 ` Daniel Jacobowitz
2002-12-12 11:15 ` Maciej W. Rozycki
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=20021204013713.D18419@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=atulsrivastava9@rediffmail.com \
--cc=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
/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