Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	"Maciej W. Rozycki" <macro@linux-mips.org>,
	Atsushi Nemoto <anemo@mba.ocn.ne.jp>,
	Linux/MIPS Development <linux-mips@linux-mips.org>
Subject: Re: [PATCH] qemu does not have dcache aliases
Date: Mon, 21 Aug 2006 19:12:16 +0100	[thread overview]
Message-ID: <20060821181216.GD20395@networkno.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0608211741580.6328@pademelon.sonytel.be>

Geert Uytterhoeven wrote:
> On Mon, 21 Aug 2006, Thiemo Seufer wrote:
> > Ralf Baechle wrote:
> > > On Mon, Aug 21, 2006 at 04:16:21PM +0100, Maciej W. Rozycki wrote:
> > > 
> > > > > Well, the QEMU cpu has 2-way 2kB dcache... does not have aliasing
> > > > > anyway. :-)
> > > > 
> > > >  I don't think emulating a bigger cache so that we can add aliases should 
> > > > be *that* difficult.  Adding aliases themselves might be a bit trickier, 
> > > > but the gain would certainly justify the hassle, wouldn't it?
> > > 
> > > The cache lookup for every access would have serious impact on performance.
> > > The question is, is it worth the price?  Would such patches be acceptable
> > > by the upstream qemu maintainers?
> > 
> > Likely not, given that performance is the prime criterion there.
> 
> It depends. If you just want to run MIPS Linux, yes.
> If you want to debug the kernel on a MIPS core with cache aliasing[*], no.

I wrote about qemu upstream's priorities.


Thiemo

  reply	other threads:[~2006-08-21 18:13 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
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 [this message]
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=20060821181216.GD20395@networkno.de \
    --to=ths@networkno.de \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=geert@linux-m68k.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@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