All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: mattjreimer@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: D-cache aliasing issue in cow_user_page
Date: Tue, 05 Dec 2006 16:59:48 -0800 (PST)	[thread overview]
Message-ID: <20061205.165948.98864221.davem@davemloft.net> (raw)
In-Reply-To: <f383264b0612051657r2b62c7acnf10b2800934ab8b3@mail.gmail.com>

From: "Matt Reimer" <mattjreimer@gmail.com>
Date: Tue, 5 Dec 2006 16:57:12 -0800

> Right, but isn't he declaring that each architecture needs to take
> care of this? So, say, on ARM we'd need to make kunmap() not a NOP and
> call flush_dcache_page() ?

No.  He is only solving a problem that occurs on HIGHMEM
configurations on systems which can have D-cache aliasing
issues.

  reply	other threads:[~2006-12-06  0:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-05  7:38 [PATCH] mm: D-cache aliasing issue in cow_user_page Matt Reimer
2006-12-05 21:24 ` David Miller
2006-12-06  0:57   ` Matt Reimer
2006-12-06  0:59     ` David Miller [this message]
2006-12-06  7:04       ` Matt Reimer
2006-12-06 21:19       ` Matt Reimer
2006-12-07  0:46         ` David Miller
2006-12-07  6:20           ` Matt Reimer
2006-12-07  7:22             ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2006-10-17  9:15 [PATCH] mm:D-cache " Dmitriy Monakhov
2006-10-19  6:33 ` Andrew Morton
2006-10-19  6:33   ` Andrew Morton
2006-10-19  7:00   ` David Miller
2006-10-19  7:00     ` David Miller, Andrew Morton
2006-10-19  7:17     ` Andrew Morton
2006-10-19  7:17       ` Andrew Morton
2006-10-19  7:22       ` David Miller
2006-10-19  7:22         ` David Miller, Andrew Morton
2006-10-19  7:41         ` Andrew Morton
2006-10-19  7:41           ` Andrew Morton

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=20061205.165948.98864221.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mattjreimer@gmail.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 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.