All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zoltan Menyhart <Zoltan.Menyhart@bull.net>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	"tony.luck@intel.com" <tony.luck@intel.com>,
	"nickpiggin@yahoo.com.au" <nickpiggin@yahoo.com.au>,
	Christoph Lameter <clameter@sgi.com>
Subject: Re: [PATCH] flush icache before set_pte() take 5.
Date: Mon, 30 Jul 2007 14:30:50 +0000	[thread overview]
Message-ID: <46ADF61A.6000509@bull.net> (raw)
In-Reply-To: <20070728150319.d19f531f.kamezawa.hiroyu@jp.fujitsu.com>

KAMEZAWA Hiroyuki wrote:

> Considerations:
>   - I can add CONFIG_MONTECITO if necessary. But it will be confusing, I think.

What about this trick below?

identify_cpu() finds out the "c->family".
If any of the CPUs has c->family=32 (and the future versions...) then
set a global flag. And:

static inline void sync_icache_dcache(pte_t pte) {
        if (pte_exec(pte) && global_flag)
                __sync_icache_dcache(pte);
}

Thanks,

Zoltan

WARNING: multiple messages have this Message-ID (diff)
From: Zoltan Menyhart <Zoltan.Menyhart@bull.net>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	"tony.luck@intel.com" <tony.luck@intel.com>,
	"nickpiggin@yahoo.com.au" <nickpiggin@yahoo.com.au>,
	Christoph Lameter <clameter@sgi.com>
Subject: Re: [PATCH] flush icache before set_pte() take 5.
Date: Mon, 30 Jul 2007 16:30:50 +0200	[thread overview]
Message-ID: <46ADF61A.6000509@bull.net> (raw)
In-Reply-To: <20070728150319.d19f531f.kamezawa.hiroyu@jp.fujitsu.com>

KAMEZAWA Hiroyuki wrote:

> Considerations:
>   - I can add CONFIG_MONTECITO if necessary. But it will be confusing, I think.

What about this trick below?

identify_cpu() finds out the "c->family".
If any of the CPUs has c->family==32 (and the future versions...) then
set a global flag. And:

static inline void sync_icache_dcache(pte_t pte) {
        if (pte_exec(pte) && global_flag)
                __sync_icache_dcache(pte);
}

Thanks,

Zoltan

  parent reply	other threads:[~2007-07-30 14:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-28  6:03 [PATCH] flush icache before set_pte() take 5 KAMEZAWA Hiroyuki
2007-07-28  6:03 ` KAMEZAWA Hiroyuki
2007-07-28  6:14 ` [PATCH] flush icache before set_pte() take 5. [1/2] cache flush in KAMEZAWA Hiroyuki
2007-07-28  6:14   ` [PATCH] flush icache before set_pte() take 5. [1/2] cache flush in migration KAMEZAWA Hiroyuki
2007-07-30 18:20   ` [PATCH] flush icache before set_pte() take 5. [1/2] cache flush Christoph Lameter
2007-07-30 18:20     ` [PATCH] flush icache before set_pte() take 5. [1/2] cache flush in migration Christoph Lameter
2007-07-28  6:15 ` [PATCH] flush icache before set_pte() take 5. [2/2] sync icache KAMEZAWA Hiroyuki
2007-07-28  6:15   ` [PATCH] flush icache before set_pte() take 5. [2/2] sync icache dcache for ia64 KAMEZAWA Hiroyuki
2007-07-30 14:30 ` Zoltan Menyhart [this message]
2007-07-30 14:30   ` [PATCH] flush icache before set_pte() take 5 Zoltan Menyhart
2007-07-31  0:29   ` KAMEZAWA Hiroyuki
2007-07-31  0:29     ` KAMEZAWA Hiroyuki

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=46ADF61A.6000509@bull.net \
    --to=zoltan.menyhart@bull.net \
    --cc=clameter@sgi.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=tony.luck@intel.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.