From: "Maciej W. Rozycki" <macro@mips.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org, David Ung <davidu@mips.com>,
Nigel Stephens <nigel@mips.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: MDI: testsuite support
Date: Tue, 26 Feb 2008 16:47:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0802261620150.24968@perivale.mips.com> (raw)
In-Reply-To: <20080226161716.GB19531@caradoc.them.org>
On Tue, 26 Feb 2008, Daniel Jacobowitz wrote:
> Let's hold off on this patch until the rest of the MDI target is
> posted, please. I appreciate your separating it into more manageable
> pieces but at the same time they are hard to consider in isolation
> and I want to be sure the whole thing goes in.
Well, I had promised to send the testsuite bits shortly, so I did it. :-)
Which "rest of the MDI target" are you specifically referring to? The
only piece I have got left is support for some obscure "set mdi" and "show
mdi" commands that should not be subcommands of "set" and "show" in the
first place as they operate on the target (which is against the principle
of the commands) and the latter also breaks "show" as used to print all
the settings.
However if you'd like to see this bit on the list as-is, then I am fine
with that, but I do not consider it ready for submission. My current
feeling is they should be reimplemented as separate commands -- while the
affected "show mdi" commands might fit a command like "info mdi", there is
apparently no corresponding command for "set mdi", so I suppose a pair of
commands like "mdi set" and "mdi show" might sound better.
Note I mean these commands are really obscure and are used things like to
peek or poke at TLB entries and cache lines "through a back door", so I
gather whoever is skilled enough to dare would know what they are doing
and get used to whatever the commands are called. In fact hardly anybody
uses them as proved by an embarrasing bug I fixed a while ago somewhere in
this area. ;-) They are occasionally useful for stuff like debugging
system bringup issues, weird cache corruption problems and suchlike.
Maciej
next prev parent reply other threads:[~2008-02-26 16:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 16:27 Maciej W. Rozycki
2008-02-26 16:24 ` Daniel Jacobowitz
2008-02-26 16:47 ` Maciej W. Rozycki [this message]
2008-02-26 16:58 ` Daniel Jacobowitz
2008-02-26 17:06 ` Maciej W. Rozycki
2008-02-26 17:10 ` Daniel Jacobowitz
2008-02-26 17:18 ` Maciej W. Rozycki
2008-02-26 17:28 ` Daniel Jacobowitz
2008-02-26 19:07 ` Maciej W. Rozycki
2008-02-27 15:49 ` Maciej W. Rozycki
2008-02-27 15:53 ` Daniel Jacobowitz
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=Pine.LNX.4.61.0802261620150.24968@perivale.mips.com \
--to=macro@mips.com \
--cc=davidu@mips.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.org \
--cc=nigel@mips.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