Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>,
	macro@linux-mips.org,
	Linux/MIPS Development <linux-mips@linux-mips.org>
Subject: Re: [PATCH] qemu does not have dcache aliases
Date: Mon, 21 Aug 2006 16:02:46 +0100	[thread overview]
Message-ID: <20060821150245.GA18963@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0608211651010.6328@pademelon.sonytel.be>

On Mon, Aug 21, 2006 at 04:51:40PM +0200, Geert Uytterhoeven wrote:

> Or become fully configurable, to make it match every single MIPS core ever
> build?

I imagine a special debug CPU type that throws exception when particular
problems such as cache aliases, stale I-cache lines, back-to-back cp0
operations and other dangerous or suspisious instructions are detected
or more complex and detailed profiling that a processor can offer.

  Ralf

  reply	other threads:[~2006-08-21 15:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-19 15:33 [PATCH] qemu does not have dcache aliases Atsushi Nemoto
2006-08-21 12:45 ` Maciej W. Rozycki
2006-08-21 12:47   ` Ralf Baechle
2006-08-21 13:59   ` Atsushi Nemoto
2006-08-21 14:46     ` Ralf Baechle
2006-08-21 14:51       ` Geert Uytterhoeven
2006-08-21 15:02         ` Ralf Baechle [this message]
2006-08-21 15:22       ` Atsushi Nemoto
2006-08-21 15:16     ` Maciej W. Rozycki
2006-08-21 15:26       ` Ralf Baechle
2006-08-21 15:36         ` Thiemo Seufer
2006-08-21 15:43           ` Geert Uytterhoeven
2006-08-21 18:12             ` Thiemo Seufer
2006-08-21 20:39               ` Ralf Baechle

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=20060821150245.GA18963@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=geert@linux-m68k.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@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