linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Zoltan Menyhart <Zoltan.Menyhart@bull.net>
Cc: linux-ia64@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org, "tony.luck@intel.com" <tony.luck@intel.com>,
	nickpiggin@yahoo.com.au, mike@stroyan.net, dmosberger@gmail.com,
	GOTO <y-goto@jp.fujitsu.com>
Subject: Re: [BUGFIX]{PATCH] flush icache on ia64 take2
Date: Fri, 6 Jul 2007 18:50:06 +0900	[thread overview]
Message-ID: <20070706185006.0014bea5.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <468E0E52.2060705@bull.net>

On Fri, 06 Jul 2007 11:41:38 +0200
Zoltan Menyhart <Zoltan.Menyhart@bull.net> wrote:

> KAMEZAWA Hiroyuki wrote:
> 
> >  Note1: icache flush is called only when VM_EXEC flag is on and 
> >         PG_arch_1 is not set.
> 
> If you have not got the page in the cache, then the new page will
> be allocated with PG_arch_1 bit off.
> You are going to flush pages which are read by HW DMA, i.e. the L2I
> of Montecito does not keep old lines for those pages anyway.
> 
yes, it's my concern. 

> ...->a_ops->readpage() of "L2I safe" file systems should set PG_arch_1
> if the CPU is ia64 and it has got separate L2I.
> 
> On the other hand, arch. independent file systems should not play with
> PG_arch_1.
> The base kernel should export a macro for the file systems...
> 
Hm, but it should be discussed in another thread... I think.
>From memory management view, flush_icache before set_pte() is sane thing.
 
-Kame

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2007-07-06  9:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06  2:29 KAMEZAWA Hiroyuki
2007-07-06  9:41 ` Zoltan Menyhart
2007-07-06  9:50   ` KAMEZAWA Hiroyuki [this message]
2007-07-19  6:56 ` KAMEZAWA Hiroyuki
2007-07-19 12:05   ` Zoltan Menyhart
2007-07-19 13:01     ` KAMEZAWA Hiroyuki
2007-07-19 13:32       ` KAMEZAWA Hiroyuki
2007-07-19 14:33         ` Zoltan Menyhart
2007-07-19 14:15       ` Zoltan Menyhart
2007-07-19 14:51         ` KAMEZAWA Hiroyuki
2007-07-19 15:18           ` Zoltan Menyhart
2007-07-20  1:51             ` KAMEZAWA Hiroyuki
2007-07-19 12:15   ` Zoltan Menyhart

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=20070706185006.0014bea5.kamezawa.hiroyu@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=Zoltan.Menyhart@bull.net \
    --cc=dmosberger@gmail.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mike@stroyan.net \
    --cc=nickpiggin@yahoo.com.au \
    --cc=tony.luck@intel.com \
    --cc=y-goto@jp.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox