public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>
Cc: jsun@mvista.com
Subject: Re: Properly implement flush_dcache_page in 2.4?  (Or is it possible?)
Date: Fri, 30 May 2003 16:00:02 -0700	[thread overview]
Message-ID: <20030530160002.D1669@mvista.com> (raw)
In-Reply-To: <20030530190929.E9419@flint.arm.linux.org.uk>; from rmk@arm.linux.org.uk on Fri, May 30, 2003 at 07:09:29PM +0100

On Fri, May 30, 2003 at 07:09:29PM +0100, Russell King wrote:
> On Fri, May 30, 2003 at 10:32:54AM -0700, Jun Sun wrote:
> > So my question is: how other CPU arches with the same problem
> > implement flush_dcache_page()?  Flushing the whole cache? Or
> > have a broken implementation and pretend it is OK?  :)
> 
> See __flush_dcache_page() in arch/arm/mm/fault-armv.c in 2.5.70.
>

Is this routine tested to be working?  At least passing a page
index as a full virtual address to flush_cache_page() looks suspicious.

In addition, I am not sure if the vma struct will show up in the
"shared" list _if_ the page is only mapped in one user process and
in kernel (for example, those pages you obtain through get_user_pages()
call).

I am not familiar with 2.5 kernel.  I was under impression that reverse
page mapping might provide an easy solution to this problem.

Jun

  reply	other threads:[~2003-05-30 22:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-30 17:32 Properly implement flush_dcache_page in 2.4? (Or is it possible?) Jun Sun
2003-05-30 18:09 ` Russell King
2003-05-30 23:00   ` Jun Sun [this message]
2003-05-30 23:14     ` Russell King
2003-05-31  0:18       ` Jun Sun
2003-05-31  7:24       ` Hugh Dickins
2003-05-31  7:52         ` Russell King
2003-05-31  8:33           ` Hugh Dickins
2003-05-31  9:19             ` Russell King
2003-05-31 10:09               ` Hugh Dickins

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=20030530160002.D1669@mvista.com \
    --to=jsun@mvista.com \
    --cc=linux-kernel@vger.kernel.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