All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Modifing memory attributes needs cache flush
Date: Thu, 10 Jan 2002 19:17:51 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805792@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805781@msgid-missing>

>>>>> On Wed, 09 Jan 2002 17:39:38 +0900 (JST), Takanori Kawano <t-kawano@ebina.hitachi.co.jp> said:

  Takanori>  If software modifies the memory attributes for a page,
  Takanori> software must flush any processor cache copies with the
  Takanori> Flush Cache(fc) instruction for the following memory
  Takanori> attribute changes: speculative/non-speculative,
  Takanori> cacheable/uncacheable(for transitions from cacheable to
  Takanori> uncacheable), and coherency. Software must flush any
  Takanori> coalescing buffers if a page is changes from coalescing to
  Takanori> any other attribute.

  Takanori> Does anybody know why the current code doesn't flush
  Takanori> cache?

Well, the kernel is supposed to use each page in a consistent fashion
(no change of attributes).  Though this isn't enforced anywhere (see
earlier discussion about write-coalescing mappings.  We need a general
solution for this eventually.  For now, it will have to be dealt with
on a case-by-case basis, I think.

	--david


      reply	other threads:[~2002-01-10 19:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-09  8:39 [Linux-ia64] Modifing memory attributes needs cache flush Takanori Kawano
2002-01-10 19:17 ` David Mosberger [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=marc-linux-ia64-105590698805792@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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.