All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Horton <phorton@bitbox.co.uk>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: pdh@colonel-panic.org, linux-mips@linux-mips.org
Subject: Re: missing flush_dcache_page call in 2.4 kernel
Date: Tue, 30 Mar 2004 10:48:42 +0100	[thread overview]
Message-ID: <4069427A.9000400@bitbox.co.uk> (raw)
In-Reply-To: <20040330.153842.48794669.nemoto@toshiba-tops.co.jp>

Atsushi Nemoto wrote:

>>>>>>On Sun, 28 Mar 2004 14:04:00 +0100, Peter Horton <pdh@colonel-panic.org> said:
>>>>>>            
>>>>>>
>pdh> I've ditched the original Cobalt hack in c-r4k.c, and am using
>pdh> the patch below instead. Seems to work okay ...
>
>+	for (; addr < (void *) end; addr += PAGE_SIZE)
>+		flush_data_cache_page((unsigned long) addr);
>
>dma_cache_wback() will be more efficient ?
>  
>
Well technically it should be dma_cache_wback_inv(), though they equate 
to the same function currently.

It would be more efficient, but the dma_cache_*() functions are only 
available under CONFIG_DMA_NONCOHERENT, and our problem has nothing to 
do with DMA coherency at all.

All we really need to do is add a flush_dcache_range(from,to) function. 
I'm working on this at the moment.

>Also, I personally think replacing all insb/insw/insl is a bit
>overkill.  I'd prefer redefine insb/insw/insl in asm-mips/ide.h, but
>I'm not sure it is enough. (really all ins[bwl] should take care of
>the cache inconsistency?)
>
>  
>
There maybe other block drivers (SCSI?) that use insb/insw/insl that 
would also cause us grief, but we could provide both versions of the 
functions and select them as necessary.

P.

      reply	other threads:[~2004-03-30  9:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-25 13:42 missing flush_dcache_page call in 2.4 kernel Atsushi Nemoto
2004-03-25 14:33 ` Ralf Baechle
2004-03-25 14:50   ` Peter Horton
2004-03-26  3:22     ` Atsushi Nemoto
2004-03-26 18:43       ` Peter Horton
2004-03-26 19:27         ` Maciej W. Rozycki
2004-03-27 13:49         ` Atsushi Nemoto
2004-03-28 13:04           ` Peter Horton
2004-03-30  6:38             ` Atsushi Nemoto
2004-03-30  9:48               ` Peter Horton [this message]

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=4069427A.9000400@bitbox.co.uk \
    --to=phorton@bitbox.co.uk \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=linux-mips@linux-mips.org \
    --cc=pdh@colonel-panic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.